Device, method, and graphical user interface for managing authentication credentials for user accounts

ABSTRACT

In accordance with some embodiments, a method is performed at an electronic device with a display device and one or more input devices. The method includes displaying, via the display device, a user interface that includes a new-password field. The method includes detecting, via the one or more input devices, a user input that corresponds to selection of the new-password field. In response to detecting the user input that corresponds to selection of the new-password field, the method includes displaying, on the display device, a representation of a new automatically-generated password in the new-password field and displaying, on the display device, an affordance to accept the new automatically-generated password and an affordance to decline to use the new automatically-generated password.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent App. No.62/679,841, filed on Jun. 3, 2018, which is incorporated by reference inits entirety.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that manage authentication credentials for useraccounts.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Example touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Example manipulations include adjusting the position and/or size of oneor more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Example user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture, iPhoto, Photos fromApple Inc. of Cupertino, Calif.), a digital content (e.g., videos andmusic) management application (e.g., iTunes from Apple Inc. ofCupertino, Calif.), a drawing application, a presentation application(e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But methods for performing these manipulations are cumbersome andinefficient. For example, using a sequence of mouse-based inputs toselect one or more user interface objects and perform one or moreactions on the selected user interface objects is tedious and creates asignificant cognitive burden on a user. In addition, these methods takelonger than necessary, thereby wasting energy. This latter considerationis particularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for managing authentication credentialsfor user accounts. Such methods and interfaces optionally complement orreplace conventional methods for managing authentication credentials foruser accounts. Such methods and interfaces reduce the cognitive burdenon a user and produce a more efficient human-machine interface. Forbattery-operated devices, such methods and interfaces conserve power andincrease the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch-screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through stylus and/or fingercontacts and gestures on the touch-sensitive surface. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsare, optionally, included in a non-transitory computer readable storagemedium or other computer program product configured for execution by oneor more processors.

In accordance with some embodiments, a method is performed at anelectronic device with a display device and one or more input devices.The method includes displaying, via the display device, a user interfacethat includes a new-password field. The method includes detecting, viathe one or more input devices, a user input that corresponds toselection of the new-password field. In response to detecting the userinput that corresponds to selection of the new-password field, themethod includes displaying, on the display device, a representation of anew automatically-generated password in the new-password field anddisplaying, on the display device, an affordance to accept the newautomatically-generated password and an affordance to decline to use thenew automatically-generated password.

In accordance with some embodiments, a method is performed at anelectronic device with a display device and one or more input devices.The method includes receiving, via the one or more input devices, arequest to access a resource protected by a verification code. Afterreceiving the request to access the resource, the method includesreceiving, at the electronic device, an electronic message. Afterreceiving the electronic message and while displaying, via the displaydevice, a user interface for inputting the verification code, the methodincludes, in accordance with a determination that the electronic messageincludes content that meets respective criteria, wherein the respectivecriteria include a format requirement that the electronic messageincludes content that matches a predetermined format, displaying aninsertion affordance that, when selected, automatically inserts thecontent that matches the predetermined format as a verification code inthe user interface.

In accordance with some embodiments, a method is performed at a firstelectronic device with a display device and one or more input devices.The method includes receiving, at the first electronic device, anindication that a second electronic device is in need of authenticationcredentials for a service. In response to receiving the indication thatthe second electronic device is in need of authentication credentialsfor the service, in accordance with a determination that the firstelectronic device meets respective criteria, wherein the respectivecriteria include a requirement that the first electronic device iswithin a predetermined proximity to the second electronic device, themethod includes displaying, via the display device in order for therespective criteria to be met, a verification prompt that requires inputof verification information from the second electronic device on thefirst electronic device in order to proceed. While displaying theverification prompt, the method includes receiving, via the one or moreinput devices, the verification information from the second electronicdevice on the first electronic device. In response to receiving theverification information, the method includes initiating a process forsharing authentication credentials for the service from the firstelectronic device to the second electronic device.

In accordance with some embodiments, a method is performed at anelectronic device with a display device and one or more input devices.The method includes detecting, via the one or more input devices, averbal request to display password information. In response to receivingthe verbal request to display the password information, the methodincludes, in accordance with a determination that the request is for apassword for a first user account that is accessible by the device andthat the user is authenticated, displaying the password for the firstuser account and, in accordance with a determination that the request isfor a password for a second user account that is accessible by thedevice and that the user is authenticated, displaying the password forthe second user account.

In accordance with some embodiments, an electronic device includes adisplay device configured to display a user interface, one or more inputdevices configured to receive user inputs, and a processing devicecoupled with the display device and the one or more input devices. Theprocessing device is configured to display, via the display device, auser interface that includes a new-password field. The processing isconfigured to detect, via the one or more input devices, a user inputthat corresponds to selection of the new-password field. In response todetecting the user input that corresponds to selection of thenew-password field, the processing device is configured to display, onthe display device, a representation of a new automatically-generatedpassword in the new-password field and display, on the display device,an affordance to accept the new automatically-generated password and anaffordance to decline to use the new automatically-generated password.

In accordance with some embodiments, an electronic device includes adisplay device configured to display a user interface, one or more inputdevices configured to receive user inputs, and a processing devicecoupled with the display device and the one or more input devices. Theprocessing device is configured to receive, via the one or more inputdevices, a request to access a resource protected by a verificationcode. After receiving the request to access the resource, the processingdevice is configured to receive, at the electronic device, an electronicmessage. After receiving the electronic message and while displaying,via the display device, a user interface for inputting the verificationcode, the processing device is configured to, in accordance with adetermination that the electronic message includes content that meetsrespective criteria, wherein the respective criteria include a formatrequirement that the electronic message includes content that matches apredetermined format, display an insertion affordance that, whenselected, automatically inserts the content that matches thepredetermined format as a verification code in the user interface.

In accordance with some embodiments, a first electronic device includesa display device configured to display a user interface, one or moreinput devices configured to receive user inputs, and a processing devicecoupled with the display device and the one or more input devices. Theprocessing device is configured to receive, at the first electronicdevice, an indication that a second electronic device is in need ofauthentication credentials for a service. In response to receiving theindication that the second electronic device is in need ofauthentication credentials for the service, in accordance with adetermination that the first electronic device meets respectivecriteria, wherein the respective criteria include a requirement that thefirst electronic device is within a predetermined proximity to thesecond electronic device, the processing device is configured todisplay, via the display device in order for the respective criteria tobe met, a verification prompt that requires input of verificationinformation from the second electronic device on the first electronicdevice in order to proceed. While displaying the verification prompt,the processing device is configured to receive, via the one or moreinput devices, the verification information from the second electronicdevice on the first electronic device. In response to receiving theverification information, the processing device is configured toinitiate a process for sharing authentication credentials for theservice from the first electronic device to the second electronicdevice.

In accordance with some embodiments, a first electronic device includesa display device configured to display a user interface, one or moreinput devices configured to receive user inputs, and a processing devicecoupled with the display device and the one or more input devices. Theprocessing device is configured to detect, via the one or more inputdevices, a verbal request to display password information. In responseto receiving the verbal request to display the password information, theprocessing device is configured to, in accordance with a determinationthat the request is for a password for a first user account that isaccessible by the device and that the user is authenticated, display thepassword for the first user account and, in accordance with adetermination that the request is for a password for a second useraccount that is accessible by the device and that the user isauthenticated, display the password for the second user account

In accordance with some embodiments, an electronic device includes adisplay device, one or more input devices, one or more processors,non-transitory memory, and one or more programs; the one or moreprograms are stored in the non-transitory memory and configured to beexecuted by the one or more processors and the one or more programsinclude instructions for performing or causing performance of theoperations of any of the methods described herein. In accordance withsome embodiments, a non-transitory computer-readable storage medium hasstored therein instructions which when executed by one or moreprocessors of an electronic device with a display device and one or moreinput devices, cause the electronic device to perform or causeperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a graphical user interface on anelectronic device with a display device, one or more input devices, amemory, and one or more processors to execute one or more programsstored in the non-transitory memory includes one or more of the elementsdisplayed in any of the methods described above, which are updated inresponse to inputs, as described in any of the methods described herein.In accordance with some embodiments, an electronic device includes: adisplay device, one or more input devices, and means for performing orcausing performance of the operations of any of the methods describedherein. In accordance with some embodiments, an information processingapparatus, for use in an electronic device with a display device and oneor more input devices, includes means for performing or causingperformance of the operations of any of the methods described herein.

Thus, electronic devices with display devices and one or more inputdevices are provided with faster, more efficient methods and interfacesfor managing authentication credentials for user accounts, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceconventional methods for managing authentication credentials for useraccounts.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an example user interface for a menu of applicationson a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display inaccordance with some embodiments.

FIGS. 5A-5AD illustrate example user interfaces for generating a newpassword for a user account and inserting a verification code into auser interface in accordance with some embodiments.

FIGS. 6A-6H illustrate example user interfaces for sharingauthentication credentials in accordance with some embodiments.

FIGS. 7A-7Y illustrate example user interfaces for displaying passwordinformation in accordance with some embodiments.

FIGS. 8A-8C are flow diagrams illustrating a method of generating a newpassword for a user account in accordance with some embodiments.

FIGS. 9A-9D are flow diagrams illustrating a method of inserting averification code into a user interface in accordance with someembodiments.

FIGS. 10A-10C are flow diagrams illustrating a method of sharingauthentication credentials in accordance with some embodiments.

FIGS. 11A-11C are flow diagrams illustrating a method of displayingpassword information in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

As the number of service providers offering services (e.g., web servicesand mobile applications) increases, the number of user accountsassociated with a user also grows. Many user accounts are associatedwith authentication credentials, such as a username and a password, thatare provided in order to access resources provided as part of theservice. Many users have difficulty remembering a large number ofusername/password combinations. Accordingly, many users choose simple,weak, and/or insecure passwords or use the same password for manydifferent user accounts, also resulting in a lack of security. Whenproviding the password to login to a user account a new device, the usermay easily forget a strong password or be required to input furtherauthentication credentials in the form of a verification code.

Accordingly, in various implementations, when provided the option togenerate a new password for a user account, a device automaticallygenerates a strong new password. Further, the device stores the newpassword for simple retrieval via a verbal request. In variousimplementations, the device shares the password (and/or otherauthentication credentials) with other devices and automaticallyrecognizes received verification codes.

Below, FIGS. 1A-1B, 2, and 3 provide a description of example devices.FIGS. 4A-4B, 5A-5AD, 6A-6H, and 7A-7Y illustrate example user interfacesfor managing authentication credentials for user accounts. FIGS. 8A-8Cillustrate a flow diagram of a method of generating a new password for auser account. FIGS. 9A-9D illustrate a flow diagram of a method ofinserting a verification code into a user interface. FIGS. 10A-10Cillustrate a flow diagram of a method of sharing authenticationcredentials in accordance with some embodiments. FIGS. 11A-11Cillustrate a flow diagram of a method of displaying passwordinformation. The user interfaces in FIGS. 5A-5AD, 6A-6H, and 7A-7Y areused to illustrate the processes in FIGS. 8A-8C, 9A-9D, 10A-10C, and11A-11C.

Example Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Example embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, iPad®,Apple TV®, and HomePod® devices from Apple Inc. of Cupertino, Calif.Other portable electronic devices, such as laptops or tablet computerswith touch-sensitive surfaces (e.g., touch-screen displays and/ortouchpads), are, optionally, used. It should also be understood that, insome embodiments, the device is not a portable communications device,but is a desktop computer with a touch-sensitive surface (e.g., atouch-screen display and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 163 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds touser-interface objects.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based onhaptic/tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In an example embodiment, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In an example embodiment, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch-sensitive display system 112 or an extension of thetouch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 163. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 163 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 163 receive tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch-sensitive display system 112, which islocated on the front of device 100.

Device 100 optionally also includes one or more accelerometers 167,gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning theposition (e.g., attitude) of the device. FIG. 1A shows sensors 167, 168,and 169 coupled with peripherals interface 118. Alternately, sensors167, 168, and 169 are, optionally, coupled with an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch-screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes a GPS (or GLONASS or other global navigationsystem) receiver for obtaining information concerning the location ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3. Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes softwarecomponents for performing various operations related to detection ofcontact (e.g., by a finger or by a stylus), such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningan intensity of the contact (e.g., the force or pressure of the contactor a substitute for the force or pressure of the contact), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one finger contactsor stylus contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts and/or stylus contacts). In someembodiments, contact/motion module 130 and display controller 156 detectcontact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 163 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and video andmusic player module 152, workout support module 142 includes executableinstructions to create workouts (e.g., with time, distance, and/orcalorie burning goals); communicate with workout sensors (in sportsdevices and smart watches); receive workout sensor data; calibratesensors used to monitor a workout; select and play music for a workout;and display, store and transmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/ormicrophone 113 (through audio circuitry 110). Information thatperipherals interface 118 receives from I/O subsystem 106 includesinformation from touch-sensitive display system 112 or a touch-sensitivesurface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events ina respective event, such as event 1 (187-1) or event 2 (187-2) include,for example, touch begin, touch end, touch movement, touch cancellation,and multiple touching. In one example, the definition for event 1(187-1) is a double tap on a displayed object. The double tap, forexample, comprises a first touch (touch begin) on the displayed objectfor a predetermined phase, a first lift-off (touch end) for apredetermined phase, a second touch (touch begin) on the displayedobject for a predetermined phase, and a second lift-off (touch end) fora predetermined phase. In another example, the definition for event 2(187-2) is a dragging on a displayed object. The dragging, for example,comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, the event definition for a respective event, suchas event 1 (187-1) or event 2 (187-2) includes a definition of an eventfor a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event, such asevent 1 (187-1) or event 2 (187-2) also includes delayed actions thatdelay delivery of the event information until after it has beendetermined whether the sequence of sub-events does or does notcorrespond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In this embodiment, as well asothers described below, a user is enabled to select one or more of thegraphics by making a gesture on the graphics, for example, with one ormore fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 163 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 163 described above with reference to FIG. 1A), sensors 359(e.g., touch-sensitive, optical, contact intensity, proximity,acceleration, attitude, and/or magnetic sensors similar to sensors 112,164, 165, 166, 167, 168, and 169 described above with reference to FIG.1A). Memory 370 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments. Similar user interfaces are, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser”; and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod”; and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Text”;        -   Icon 426 for calendar module 148, labeled “Calendar”;        -   Icon 428 for image management module 144, labeled “Photos”;        -   Icon 430 for camera module 143, labeled “Camera”;        -   Icon 432 for online video module 155, labeled “Online            Video”;        -   Icon 434 for stocks widget 149-2, labeled “Stocks”;        -   Icon 436 for map module 154, labeled “Map”;        -   Icon 438 for weather widget 149-1, labeled “Weather”;        -   Icon 440 for alarm clock widget 169-6, labeled “Clock”;        -   Icon 442 for workout support module 142, labeled “Workout            Support”;        -   Icon 444 for notes module 153, labeled “Notes”; and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely examples. For example, in some embodiments, icon 422 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Device 300also, optionally, includes one or more contact intensity sensors (e.g.,one or more of sensors 359) for detecting intensity of contacts ontouch-sensitive surface 451 and/or one or more tactile output generators359 for generating tactile outputs for a user of device 300.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Althoughmany of the examples that follow will be given with reference to inputson touch screen display 112 (where the touch sensitive surface and thedisplay are combined), in some embodiments, the device detects inputs ona touch-sensitive surface that is separate from the display, as shown inFIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 inFIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to aprimary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). Inaccordance with these embodiments, the device detects contacts (e.g.,460 and 462 in FIG. 4B) with the touch-sensitive surface 451 atlocations that correspond to respective locations on the display (e.g.,in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In thisway, user inputs (e.g., contacts 460 and 462, and movements thereof)detected by the device on the touch-sensitive surface (e.g., 451 in FIG.4B) are used by the device to manipulate the user interface on thedisplay (e.g., 450 in FIG. 4B) of the multifunction device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or a stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device (PMD) 100 or device 300,with a display, a touch-sensitive surface, and one or more sensors todetect intensity of contacts with the touch-sensitive surface.

FIGS. 5A-5K illustrate example user interfaces for generating a newpassword for a user account in accordance with some embodiments. FIGS.5L-5AD illustrate example user interfaces for inserting a verificationcode into a user interface in accordance with some embodiments. FIG.6A-6H illustrate example user interfaces for sharing authenticationcredentials in accordance with some embodiments. FIG. 7A-7Y illustrateexample user interface for displaying password information in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIGS. 8A-8C, 9A-9D, 10A-10C, and 11A-11C. Although some of the exampleswhich follow will be given with reference to inputs on a touch-screendisplay (where the touch-sensitive surface and the display arecombined), in some embodiments, the device detects inputs on atouch-sensitive surface 451 that is separate from the display 450, asshown in FIG. 4B.

FIG. 5A illustrates a web browser user interface 502 as part of a userinterface 500 displayed by a portable multifunctional device 100(hereinafter “device 100”). The user interface 500 includes, in additionto the web browser user interface 502, a device bar 501 at the top ofthe display including an identifier of the device 100 (e.g., “iPhone”),a wireless connection indicator, a current time, and a battery indicatorindicating a charge level of the device 100.

The user interface 500 includes, below the device bar 501, and spanningthe rest of the display, a web browser user interface 502. The webbrowser user interface 502 includes an address bar 521 and a contentregion 522. The address bar 521 includes the address (e.g., a URL) of awebpage having content displayed in the content region 522. The addressbar 521 also includes a reload affordance that, when selected, reloadsthe content of the webpage in the content region 522. In FIG. 5A, theaddress bar 521 displays the address of a homepage of a service.

In FIG. 5A, the content displayed in the content region 522 includes animage (of an apple), a sign-up affordance 531A, and a sign-in affordance531B. The sign-up affordance 531A, when selected, allows a user toregister with the service, e.g., create a user account for the service,in order to access resources (e.g., content) protected by authenticationcredentials of the user account. The sign-in affordance 531B, whenselected, allows a user to provide authentication credentials to accessthe resources of the service.

FIG. 5A illustrates a contact 550A detected at a location of the sign-upaffordance 531A.

FIG. 5B illustrates the user interface 500 of FIG. 5A in response todetecting the contact 550A at the location of the sign-up affordance531A. In FIG. 5B, the address bar 521 includes the address of a sign-uppage of the web service. In FIG. 5B, the content region 522 includes theimage (of an apple), a plurality of fields 532A-532D for receiving textinput, text respectively associated with and describing the plurality offields 532A-532D, and a complete-sign-up affordance 531C that, whenselected, creates a user account with the authentication credentialsinput into the plurality of fields 532A-532D.

The plurality of fields 532A-532D includes a new-username field 532A forreceiving text input indicative of a username to be associated with auser account. The plurality of fields 532A-532D includes a phone numberfield 532B for receiving text input indicative of a phone number (e.g.,a phone number of the device 100 and/or the user) to be associated withthe user account. The plurality of fields 532A-532D includes anew-password field 532C for receiving text input indicative of apassword to be associated with the user account. The plurality of fields532A-532D includes a password-confirmation field 532D for receiving textinput matching the password input into the new-password field 532C.

FIG. 5B illustrates a contact 550B detected at a location of thenew-username field 532A.

FIG. 5C illustrates the user interface 500 of FIG. 5B in response todetecting the contact 550B at the location of the new-username field532A. In response to detecting selection of the new-username field 532A,the content region 522 includes a cursor 533 displayed in thenew-username field 532A. Further, the user interface 500 includes a softkeyboard 503A with a plurality of character insertion affordances that,when selected, inserts a respective character into the selected field.The soft keyboard 503A includes a navigation region 541. The navigationregion 541 includes a previous affordance (indicated with an up arrow)that, when selected, selects and moves the cursor 533 to a previousfield; a next affordance (indicated with a down arrow) that, whenselected, selects and moves the cursor 533 to a next field; and a doneaffordance (indicated with text reading “Done”) that, when selected,deselects the selected field and ceases display of the cursor 533 andthe soft keyboard 503A.

The soft keyboard 503A includes a text suggestion region 542 thatincludes text suggestion affordances that indicate suggested text andthat, when selected, inserts the suggested text into the selected field.

FIG. 5C illustrates a contact 550C at a location of one of the pluralityof character insertion affordances of the soft keyboard 503A.

FIG. 5D illustrates the user interface 500 of FIG. 5C in response todetecting the contact 550C at the location of the one of the pluralityof character insertion affordances (and additional contacts at others ofthe character insertion affordances to complete insertion of theusername “jappleseed” in the new-username field 532A).

FIG. 5D illustrates a contact 550D detected at the location of the phonenumber field 532B.

FIG. 5E illustrates the user interface 500 of FIG. 5D in response todetecting the contact 550D at the location of the phone number field532B. In response to detecting selection of the phone number field 532B,the cursor 533 is displayed in the phone number field 532B. Further, thesoft keyboard 503A is replaced by a numeric soft keyboard 503B with aplurality of character insertion affordances that, when selected,inserts a respective numeric character into the selected field. Like thesoft keyboard 503A, the numeric soft keyboard 503B includes thenavigation region 541 and the text suggestion region 542.

FIG. 5E illustrates a contact 550E detected at the location of one ofthe plurality of character insertion affordances.

FIG. 5F illustrates the user interface 500 of FIG. 5E in response todetecting the contact 550E at the location of the one of the pluralityof character insertion affordances (and additional contacts at others ofthe character insertion affordances to complete insertion of the phonenumber “(408) 555-1234” in the phone number field 532B).

FIG. 5F illustrates a contact 550F detected at the location of thenew-password field 532C.

FIG. 5G1 illustrates a first embodiment of the user interface 500 ofFIG. 5F in response to detecting the contact 550F at the location of thenew-password field 532C. In response to detecting selection of thenew-password field 532C, the cursor 533 ceases to be displayed. Thus,the cursor 533 is not displayed in the new-password field 532C. Rather,a representation of an automatically-generated password is displayed inthe new-password field 532C (and the password-confirmation field 532D).Further, the numeric soft keyboard 503B is replaced by a new-passworduser interface 503C (also referred to as a “password keyboard” or a“password soft keyboard”). In various implementations, the new-passworduser interface 503C is displayed at the bottom of the display, e.g., inthe same location as the soft keyboard 503A and/or numeric soft keyboard503B.

In various implementations, the automatically-generated password isgenerated by the device 100 based on one or more password constraints ofthe user interface, e.g., include at least a threshold number ofcharacters, at least one capital letter, at least one number, and/or atleast one special character. In various implementations, the device 100determines the one or more password constraints based on text in thecontent region 522 of the user interface 500 and/or other informationprovided by the service.

The new-password user interface 503C includes text 544 including adescription of the new automatically-generated password and instructionsfor retrieval of the new automatically-generated password. For example,the text 544 indicates that the new automatically-generated password hasbeen automatically generated and satisfies a password strengthrequirement. The text 544 indicates that the new automatically-generatedpassword will be saved by the device 100 and can be accessed by theuser, e.g., via a verbal request as described in further detail below.

The new-password user interface 503C includes an accept affordance 543Ato accept the new automatically-generated password and a declineaffordance 543B to decline to use the new automatically-generatedpassword. A secondary decline affordance 543BB to decline to use the newautomatically-generated password is displayed separate from thenew-password user interface 503C, in particular, next to therepresentation of the new automatically-generated password in thenew-password field 532C.

In response to selection of a particular field, the device 100determines whether to display the soft keyboard 503A (as in FIG. 5C),the numeric soft keyboard 503B (as in FIG. 5E), or the new-password userinterface 503C based on a type of the particular field. In variousimplementations, the device 100 determines the type of the field using afield detection and classification algorithm. In variousimplementations, the device 100 classifies a field based on one or moreof (1) text associated with the content in the content region 522 of theuser interface 500 or (2) a number of fields in the content region 522of the user interface 500. For example, in response to detecting a fieldlocated next to text including the word “password” and in response todetecting “register” or “sign up” in the text in content region 522, thedevice classifies the field as a new-password field (and displays thenew-password user interface 503C). In contrast, in response to detectinga field located to text including the word “password” and in response todetecting “log in” or “sign in” in the text in the content region 522,the device classifies the field as a password field (and displays a softkeyboard 503A for receiving user input of the password or automaticallyinserting a known password into the password field). As another example,in response to detecting two fields in the content region 522, one ofwhich is located next to text including the word “password,” the device100 classifies the field as a password field for signing in to a useraccount. In contrast, in response to detecting more than two fields inthe content region 522, one of which is located next to text includingthe word “password,” the device classifies the field as a new-passwordfield for creating a user account. Similarly, in response to detectingat least two fields in the content region 522, two of which are locatednext to text including the word “password,” the device 100 classifiesthe first field as a new-password field and the second field as apassword-confirmation field.

In FIG. 5G1, the representation of the new automatically-generatedpassword displayed in the new-password field 532C is the newautomatically-generated password itself. FIG. 5G2 illustrates a secondembodiment of the user interface 500 of FIG. 5F in response to detectingthe contact 550F at the location of the new-password field 532C whichdiffers from FIG. 5G1 in that the representation of the newautomatically-generated password displayed in the new-password field532C (and the password-confirmation field 532D) is a generic passwordindicator, e.g., a series of asterisks or bullets. FIG. 5G3 illustratesa third embodiment of the user interface 500 of FIG. 5F in response todetecting the contact 550F at the location of the new-password field532C which differs from FIG. 5G1 in that the representation of the newautomatically-generated password displayed in the new-password field532C (and the password-confirmation field 532D) is a portion of the newautomatically-generated password and an indication that a portion of thenew automatically-generated password is not displayed, e.g., thevisibility of the new automatically-generated password decreases alongits length by fading. In some embodiments, the newautomatically-generated password is displayed with an ellipse (e.g.,“Y2v′GS . . . ”).

FIG. 5G3 illustrates a contact 550G detected at the location of thedecline affordance 543B.

FIG. 5H illustrates the user interface 500 of FIG. 5G3 in response todetecting the contact 550G at the location of the decline affordance543B (or, in various implementations, a contact at the location of thesecondary decline affordance 543BB). In response to detecting selectionof the decline affordance 543B, the new-password user interface 503C(including the accept affordance 543A and decline affordance 543B) isreplaced with a soft keyboard 503A including a plurality of characterinsertion affordances. Further, the cursor 533 is displayed in thenew-password field 532C.

In various implementations (as in FIG. 5H), in response to detectingselection of the decline affordance 543B, the representation of the newautomatically-generated password ceases to be displayed. Accordingly, byusing the soft keyboard 503A, a user can input a password created and/orchosen by the user. In various implementations, the representation ofthe new automatically-generated password remains displayed. Accordingly,by using the soft keyboard 503A, a user can edit the newautomatically-generated password to the user's preferences or to complywith requirements for the new password, e.g., a requirement that certaincharacters (e.g., a question mark or an asterisk) not be used.

FIG. 5I illustrates the user interface 500 of FIG. 5G3 with a contact550H detected at the location of the accept affordance 543A (rather thanthe contact 550G detected at the location of the decline affordance543B).

FIG. 5J illustrates the user interface 500 of FIG. 5I in response todetecting the contact 550H at the location of the accept affordance543A. In response to detecting selection of the accept affordance 543A,the new-password user interface 503C (including the accept affordance543A and the decline affordance 543B) ceases to be displayed.

FIG. 5J illustrates a contact 550I detected at the location of thecomplete-sign-up affordance 531C.

FIG. 5K illustrates the user interface 500 of FIG. 5J in response todetecting the contact 550I at the location of the complete-sign-upaffordance 531C. In FIG. 5K, the address bar 521 includes the address ofa completed-sign-up page of the service. In FIG. 5K, the content region522 includes the image (of an apple), text indicating that aregistration process is complete, and home affordance 531D that, whenselected, returns the web browser user interface 502 to the homepage ofthe web service.

FIG. 5K illustrates a contact 550J detected at the location of the homeaffordance 531D.

FIG. 5L illustrates the user interface 500 of FIG. 5K in response todetecting the contact 550J at the location of the home affordance 531D.In FIG. 5K, the address bar 521 includes the address of the homepage andthe content displayed in the content region 222 includes the image (ofan apple), the sign-up affordance 531A, and the sign-in affordance 531B.

FIG. 5L illustrates a contact 550K detected at the location of thesign-in affordance 531B.

FIG. 5M illustrates the user interface 500 of FIG. 5L in response todetecting the contact 550K at the location of the sign-in affordance531B. In FIG. 5M, the address bar 521 includes the address of a sign-inpage of the service. In FIG. 5M, the content region 522 includes theimage (of an apple), a plurality of fields 532E-532F for receiving textinput, text respectively associated with and describing the plurality offields 532E-532F, and a continue-sign-in affordance 531E that, whenselected, requests access to the resources of the service based onauthentication credentials input into the plurality of fields 532E-532F.

The plurality of fields 532E-532F includes a username field 532E forreceiving text input indicative of a username associated with anexisting user account. The plurality of fields 532E-532F includes apassword field 532F for receiving text input indicative of a passwordassociated with the user account. In FIG. 5M, the username field 532Eand password field 532F have been automatically populated based on thedetection and classification of the fields 532E-532F and authenticationcredentials stored by the device 100.

FIG. 5M illustrates a contact 550L at a location of the continue-sign-inaffordance 531E.

FIG. 5N illustrates the user interface 500 of FIG. 5M in response todetecting the contact 550L at the location of the continue-sign-inaffordance 531E. In FIG. 5N, the address bar 521 includes the address ofa verification page of the service. In FIG. 5N, the content region 522includes the image (of an apple), a verification code field 532G forreceiving text input, text respectively associated with and describingthe verification code field 532G, and another continue-sign-inaffordance 531F that, when selected, requests access to the resources ofthe service based on authentication credentials, in particular, averification code, input into the verification code field 532G. Thecontent region 522 also includes a request-code affordance 531G that,when selected, requests that an electronic message including averification code be sent to the user, e.g., as a text message sent tothe phone number provided in FIG. 5E.

FIG. 5O illustrates the user interface 500 of FIG. 5N after anelectronic message is received by the device 100. In response toreceiving the electronic message, a message notification 561A isdisplayed. The message notification 561A includes text indicating asource of the electronic message (e.g., phone number “987-66”) andpreview text previewing the content of the electronic message.

FIG. 5O illustrates a contact 550M detected at a location of the messagenotification 561A.

FIG. 5P illustrates the user interface 500 of FIG. 5O in response todetecting the contact 550M at the location of the message notification561A. The user interface 500 includes, below the device bar 501, anavigation bar 505 including a return affordance 506 that, whenselected, returns to the web browser user interface 502. The userinterface 500 includes, below the navigation bar 505 and spanning therest of the display, a text messenger user interface 504. The textmessenger user interface 504 includes a contact bar 562 and a contentregion 563. The contact bar 562 includes text indicating a source of thecontent displayed in the content region 563. The contact bar 562 alsoincludes a back affordance (indicated with a “<”) that, when selected,displays a list of contact affordances for accessing content (e.g., SMStext messages) provided by respective contacts. The contact bar 562 alsoincludes an information affordance (a circled “i”) that, when selectedprovides information regarding the source of the content displayed inthe content region 563.

The content region 563 includes a message window 564 including thecontent of the electronic message received from the source. In themessage window 564, content of the text message that meet respectivecriteria is displayed in a different manner than the remainder of thecontent (e.g., is emphasized). In particular, in FIG. 5P, content of thetext message that meet respective criteria is displayed as underlined,whereas the remainder of the content is not underlined. In variousimplementations, the content of the text message that meet respectivecriteria is displayed in a different color (e.g., blue) than theremainder of the content (e.g., black). In various implementations, therespective criteria include an e-mail format requirement that thecontent matches an e-mail format (e.g., includes characters preceding anat sign (“@”) and characters following the at sign.) In variousimplementations, the respective criteria includes a phone number formatrequirement that the content matches a phone number format (e.g.,includes at least a threshold number of numeric characters). In variousimplementations, the respective criteria include a verification codeformat requirement that the content matches a verification code format(e.g., a numeric or an alphanumeric value, such as 123456 or ab3d5f, inclose proximity to a keyword or short group of words denoting thepresence of a security code, such as “passcode”, “authentication code”,“2FA”, “is your <service name> code” or “to confirm your account”).

FIG. 5P illustrates a contact 550N detected at the location of contentdisplayed in the message window 564 meeting a phone number formatrequirement.

FIG. 5Q illustrates the user interface 500 of FIG. 5P in response todetecting the contact 550N at the location of content displayed in themessage window 564 meeting a phone number format requirement. In FIG.5Q, the user interface 500 includes a phone call window 565A includingtext indicating a phone number, a call affordance 566A that, whenselected, causes the device 100 to place a telephone call to the phonenumber, and a cancel affordance 566B that, when selected, dismisses thephone call window 565A.

FIG. 5Q illustrates a contact 550O detected at the location the cancelaffordance 566B.

FIG. 5R illustrates the user interface 500 of FIG. 5Q in response todetecting the contact 550O at the location of the cancel affordance566B. In FIG. 5R, the phone call window 565A ceases to be displayed.

FIG. 5R illustrates a contact 550P at the location of content displayedin the message window 564 meeting a verification code formatrequirement.

FIG. 5S illustrates the user interface 500 of FIG. 5R in response todetecting the contact 550P at the location of content displayed in themessage window 564 meeting the verification code format requirement. InFIG. 5S, the user interface 500 includes a verification code window 565Bincluding text indicating a verification code, a copy affordance 566Cthat, when selected, causes the device 100 to store the verificationcode in a cache (e.g., to copy the verification code to a clipboard),and a cancel affordance 566D that, when selected, dismisses theverification code window 565B.

FIG. 5S illustrates a contact 550P detected at the location of the copyaffordance 566C.

FIG. 5T illustrates the user interface 500 in response to detecting thecontact 550P at the location of the copy affordance 566C. In FIG. 5T,the verification code window 565B ceases to be displayed.

FIG. 5T illustrates a contact 550Q detected at the location of thereturn affordance 506.

FIG. 5U1 illustrates the user interface 500 in response to detecting thecontact 550Q at the location of the return affordance 506. In FIG. 5U1,the text messenger user interface 504 is replaced with the web browseruser interface 502 of FIG. 5N. Accordingly, FIG. 5U1 differs from FIG.5N in that, unillustrated, the device 100 has received an electronicmessage and has stored the verification code in a cache (e.g., copiedthe verification code to a clipboard).

As compared to FIG. 5O, FIG. 5U2 illustrates another embodiment of theuser interface 500 of FIG. 5N after an electronic message is received bythe device 100. In response to receiving the electronic message, amessage notification 561B is displayed. The message notification 561Bincludes text indicating a source of the electronic message (e.g., phonenumber “987-66”) and preview text previewing the content of theelectronic message. The message notification 561B also includes, inresponse to detecting content of the electronic message meetingrespective criteria include a verification code format requirement, acopy affordance 561C that, when selected, causes the device 100 to storethe verification code in a cache (e.g., to copy the verification code toa clipboard), and a read affordance 561D that, when selected, dismissesthe message notification 561B.

FIG. 5U2 illustrates a contact 550R detected at the location of the copyaffordance 561C.

FIG. 5U3 illustrates the user interface 500 of FIG. 5U2 in response todetecting the contact 550R at the location of the copy affordance 561C.The user interface 500 of FIG. 5U3 is the same as the user interface 500of FIG. 5U1.

FIG. 5U3 illustrates a contact 550S detected at the location of theverification code field 532G.

FIG. 5V illustrates the user interface 500 of FIG. 5U3 (or, similarly,of FIG. 5U1) in response to detecting the contact 550S at the locationof the verification code field 532G. In response to detecting selectionof the verification code field 532G, the cursor 533 is displayed in theverification code field 532G. Further, the user interface 500 includesthe numeric soft keyboard 503B.

In response to including text stored in the cache, e.g., copied to theclipboard, the user interface 500 includes a paste affordance 534 that,when selected, inserts the text stored in the cache into the selectedfield.

FIG. 5V illustrates a contact 550T detected at the location of the pasteaffordance 534.

FIG. 5W illustrates the user interface 500 of FIG. 5V in response todetecting the contact 550T at the location of the paste affordance 534.In FIG. 5W, the verification code from the cache has been inserted intothe verification code field 532G.

FIG. 5W illustrates a contact 550U detected at the location of thecontinue-sign-in affordance 531F.

FIG. 5X illustrates the user interface 500 of FIG. 5W in response todetecting the contact 550U at the location of the continue-sign-inaffordance 531F. In FIG. 5X, the address bar 521 includes the address ofa content page of the service. In FIG. 5X, the content region 522includes resources provided by the service protected by authenticationcredentials (potentially including the verification code).

As compared to FIG. 5O, FIG. 5Y illustrates another embodiment of theuser interface 500 of FIG. 5N after an electronic message is received bythe device 100. In response to receiving the electronic message, amessage notification 561A is displayed. The message notification 561Aincludes text indicating a source of the electronic message (e.g., phonenumber “987-66”) and preview text previewing the content of theelectronic message.

Whereas FIG. 5O illustrates a contact 550M at the location of themessage notification 561A, FIG. 5Y illustrates a contact 550V at thelocation of the verification code field 532G.

FIG. 5Z illustrates the user interface of FIG. 5Y in response todetecting the contact 550V at the location of the verification codefield 532G. In response to detecting selection of the verification codefield 532G, the cursor 533 is displayed in the verification code field532G. Further, the user interface 500 includes the numeric soft keyboard503B. The numeric soft keyboard 503B includes the navigation region 541and the text suggestion region 542. In accordance that respectivecriteria are met, the text suggestion region 542 includes an insertionaffordance 545 that, when selected, automatically inserts theverification code in the verification code field 532G. Although FIG. 5Zillustrates the numeric soft keyboard 503B, in various implementations,the insertion affordance 545 is displayed in a text suggestion region542 above the soft keyboard 503A, a handwriting recognition userinterface, or other user input region.

In various implementations, the respective criteria include arequirement that the electronic message includes content that meets averification code format requirement. In various implementations, therespective criteria include a timing requirement that the user interfaceis displayed within a predetermined time period from when the electronicmessage was received. Thus, in various implementations, the insertionaffordance is only displayed for a limited time from when the electronicmessage is received, e.g., three minutes. In various implementations,the respective criteria include a characteristic requirement that theuser interface includes a text entry field having predeterminedcharacteristics. In various implementations, the respective criteriaincludes a selection requirement that a text entry field is selected.For example, the insertion affordance 545 is displayed when a field isselected that is classified as a verification code field (e.g., based onanalysis or metadata regarding the field provided by the service). Asanother example, the insertion affordance 545 is only displayed when afield is selected that is not otherwise classified as, e.g., username,password, e-mail address, phone number, credit card number, address,multi-line input field, etc.

In various implementations, the insertion affordance 545 includes anindication of the application by which the electronic message wasreceived. For example, in FIG. 5Z, the insertion affordance 545indicates a text messaging application (“Messages”). In otherimplementations, the insertion affordance indicates an e-mailapplication or a chat application. In various implementations, theinsertion affordance 545 includes an indication of the sender of theelectronic message. For example, in FIG. 5Z, the insertion affordanceindicates a phone number (“987-66”). In other implementations, theinsertion affordance indicates a name of the service, e.g. “Apple Fun.”In some embodiments, the indication of the application or the indicationof the sender is not displayed with the other.

FIG. 5Z illustrates a contact 550W at the location of the insertionaffordance in the text suggestion region 542.

FIG. AA illustrates the user interface 500 of FIG. 5Z in response todetecting the contact 550W at the location of the insertion affordance545. In FIG. 5AA, the verification code has been inserted into theverification code field 532G.

In various implementations, the user interface 500 of FIG. 5AA isreached directly from the user interface of FIG. 5Y, without requiring aselection of the insertion affordance 545. Thus, in variousimplementations, in response to the determination that the electronicmessage includes content that meets the respective criteria, the device100 automatically inserts the content as a verification code in the userinterface.

As compared to FIG. 5O, FIG. 5AB illustrates another embodiment of theuser interface 500 of FIG. 5N after an electronic message is received bythe device 100. In contrast to FIG. 5O, in response to receiving theelectronic message, no message notification 561A is displayed. Further,in response to the determination that the electronic message includescontent that meets the verification code format requirement, withoutdisplay or selection of an insertion affordance 545, the device 100automatically inserts the content as a verification code in theverification code field 532G.

As compared to FIG. 5O, FIG. 5AC illustrates another embodiment of theuser interface 500 of FIG. 5N after an electronic message is received bythe device 100. In response to receiving the electronic message, amessage notification 561F is displayed. The message notification 561Fincludes text indicating a source of the electronic message (e.g.,contact name “Gary”) and preview text previewing the content of theelectronic message. In contrast to FIG. 5O, the content of theelectronic message does not include content meeting respective criteria.In particular, the content of the electronic message does not includecontent meeting a verification code format requirement. Accordingly, themessage notification 561C 561F does not include a copy affordance 561C,but rather, includes a reply affordance 561E for composing a textmessage reply to the sender of the electronic message.

FIG. 5AC illustrates a contact 550X at the location of the verificationcode field 532G.

FIG. 5AD illustrates the user interface 500 of FIG. 5AC in response todetecting the contact 550X at the location of the verification codefield 532G. In response to detecting selection of the verification codefield 532G, the content region 522 includes the cursor 533 displayed inthe verification code field 532G. Further, the user interface 500includes a soft keyboard 503A with a plurality of character insertionaffordances that, when selected, inserts a character into the selectedfield. The soft keyboard 503A includes navigation region 541 and a textsuggestion region 542 which includes text suggestion affordances thatindicate suggested text and that, when selected, inserts the suggestedtext into the selected field. In FIG. 5AD, in contrast to FIG. 5Z, thetext suggestion region 542 does not include an insertion affordance 545for inserting a verification code because the electronic messagedisplayed in the message notification 561F of FIG. 5AC did not include averification code.

FIG. 6A illustrates an operating environment 600 including a firstelectronic device 610, a second electronic device 620, and a thirdelectronic device 630. The first electronic device 610 corresponds to aportable electronic device, such as the portable electronic device 100of FIG. 1 or the device 300 of FIG. 3. The first electronic device 610includes a display that provides a first user interface 612. The secondelectronic device 620 is a media playback device coupled to a displaydevice 621 that provides a second user interface 622. The thirdelectronic device 630 is a remote control for the second electronicdevice 620. The third electronic device 630 includes a touch-sensitiveinput device 631 for producing user inputs that are transmitted to thesecond electronic device 620.

The second user interface 622 includes a plurality of affordances that,when selected, open applications or provide media content via the seconduser interface 622. In FIG. 6A, an application affordance 623 of theplurality of affordances is selected.

FIG. 6A illustrates a contact 650A detected on the touch-sensitive inputdevice 631 while the application affordance 623 is selected.

FIG. 6B illustrates the operating environment 600 of FIG. 6A in responseto detecting the contact 650A on the touch-sensitive input device 631while the application affordance 623 is selected. In FIG. 6B, the seconduser interface 622 includes a home screen of a service that includes animage (of an apple), a sign-up affordance 624A, and a sign-in affordance624B. The sign-up affordance 624A, when selected, allows a user toregister with the service, e.g., create a user account, to accessresources (e.g., content) protected by authentication credentials of theuser account. The sign-in affordance 624B, when selected, allows a userto provide authentication credentials to access the resources of theservice. In FIG. 6B, the sign-in affordance 624B is selected.

FIG. 6B illustrates a contact 650B detected on the touch-sensitive inputdevice 631 while the sign-in affordance 624B is selected.

FIG. 6C illustrates the operating environment 600 of FIG. 6B in responseto detecting the contact 650B on the touch-sensitive input device 631while the sign-in affordance 624B is selected. In FIG. 6C, the seconduser interface 622 includes a sign-in screen of the service thatincludes an image (of an apple), a username field 625A for receivingtext input indicative of a username associated with an existing useraccount, and a password field 625B for receiving text input indicativeof a password associated with the user account. The second userinterface 622 includes a continue-sign-in affordance 624C that, whenselected, requests access to the resources of the service based onauthentication credentials input into the fields 625A-625B.

In FIG. 6C, the second electronic device 620 transmits, to the firstelectronic device 610, an indication that the second electronic device620 is in need of authentication credentials for a service (e.g., ausername and password).

FIG. 6D illustrates the first electronic device 610 in response toreceiving the indication that the second electronic device 620 is inneed of authentication credentials for a service. In FIG. 6D, the firstuser interface 612 includes the device bar 501 and an applicationlauncher user interface 507. The application launcher user interface 507includes a plurality of representations of applications installed on thefirst electronic device 610 arranged in a grid. In front of theapplication launcher user interface 507 (or any other user interfacecurrently displayed), the first user interface 612 includes a sharingconfirmation window 640.

The sharing confirmation window 640 includes text describing theindication that the second electronic device 620 is in need ofauthentication credentials for a service. In various implementations,the text includes an indication of the service (e.g., “Apple Fun”). Invarious implementations, the text generically indicates that the secondelectronic device 620 is in need of authentication credentials for aservice (e.g., “Johnny's AppleTV is requesting a password.”) The sharingconfirmation window 640 includes a sharing confirmation affordance 641that, when selected, allows the sharing of credentials between the firstelectronic device 610 and the second electronic device 620 as describedfurther below. The sharing confirmation window 640 includes a sharingcancelation affordance 642 that, when selected, disallows the sharing ofcredentials between the first electronic device 610 and the secondelectronic device 620.

In various implementations, the sharing confirmation window 640 isdisplayed on the first electronic device 610 in accordance with adetermination that the first electronic device 610 is within apredetermined proximity to the second electronic device 620. In variousimplementations, the predetermined proximity is the distance to theclosest device. In various implementations, the predetermined proximityis a predetermined range. In various implementations, the sharingconfirmation window 640 is displayed on the first electronic device 610in accordance with a determination that the first electronic device 610is within a predetermined proximity to the third electronic device 630associated with the second electronic device 620. In variousimplementations, the predetermined proximity is the distance to theclosest device. In various implementations, the predetermined proximityis a predetermined range.

FIG. 6D illustrates a contact 650C detected at the location of thesharing confirmation affordance 641.

FIG. 6E illustrates the operating environment 600 of FIG. 6C in responseto detecting the contact 650C at the location of the sharingconfirmation affordance 641. In FIG. 6E, the second user interface 622displays verification information, e.g., an authorization code. In FIG.6E, the first user interface 612 displays a verification prompt thatrequires input of information from the second electronic device 620(e.g., the verification information displayed by the second electronicdevice 620) on the first electronic device 610 in order to proceed. Inparticular, the verification prompt is for establishing a secureconnection between the first electronic device 610 and the secondelectronic device 620. The verification prompt includes a plurality ofnumeric character affordances for inputting the information from thesecond electronic device 620 (e.g., the verification informationdisplayed by the second electronic device 620). In variousimplementations, the verification prompt includes a soft keyboard, suchas the soft keyboard 503B, or other input user interface.

FIG. 6E illustrates a contact 650D at a location of one of the pluralityof numeric character affordances.

FIG. 6F illustrates first electronic device 610 in response to detectingthe contact 650D at the location of the one of the plurality of numericcharacter affordances and other contacts corresponding to theverification information from the second electronic device 620. Thefirst user interface 612 includes the device bar 501 and a serviceselection user interface 508. The service selection user interface 508includes a list of service affordances 661A-661G respectively associateda plurality of services, user accounts for those services, andauthentication credentials for those user accounts. The serviceselection user interface 508 includes a search field 662 for receiving atext input and searching the plurality of services based on the textinput.

In FIG. 6F, the list of service affordances 661A-661G is sorted based atleast in part on relevance of the respective services. In particular,the indication that the second electronic device 620 is in need ofauthentication credentials for a service indicates the service and thatservice is listed at the top of the list of service affordances661A-661G.

FIG. 6F illustrates a contact 650E detected at the location of a firstservice affordance 661A of the list of service affordance 661A-661G.

FIG. 6G illustrates the operating environment 600 of FIG. 6E in responseto detecting the contact 650E at the location of the first serviceaffordance 661A. In FIG. 6G, in the second user interface 622, theusername field 625A and the password field 625B are populated withauthentication credentials received from the first electronic device610. Further, the sign-in affordance 624C is selected. In the first userinterface 612, a complete-sharing window 643 is displayed including anotification indicating that the authentication credentials having beenshared with the second electronic device 620.

FIG. 6G illustrates a contact 650F detected on the touch-sensitive inputdevice 631 while the continue-sign-in affordance 624C is selected.

FIG. 6H illustrates the operating environment 600 of FIG. 6G in responseto detecting the contact 650F on the touch-sensitive input device 631while the continue-sign-in affordance 624C is selected. In FIG. 6H, thesecond user interface 622 includes a content screen of the service.

FIG. 7A illustrates an application launcher user interface 707 as partof a user interface 700 displayed by a portable multifunctional device100 (hereinafter “device 100”). The user interface 700 includes, inaddition to the application launcher user interface 507, a device bar701 at the top of the display including an identifier of the device 100(e.g., “iPhone”), a wireless connection indicator, a current time, and abattery indicator indicating a charge level of the device 100.

The user interface 700 includes, below the device bar 701, and spanningthe rest of the display, an application launcher user interface 707. Theapplication launcher user interface 707 includes a plurality ofrepresentations of applications installed on the device 100, including asettings representation 710. As shown in FIG. 7A, each representationincludes an icon associated with the corresponding application and textdescribing the application (e.g., a name or function of theapplication). As an application launching user interface 707, inresponse to detecting a user input at the designated location of therepresentation of a particular application, the device 100 launches theparticular application.

Although FIG. 7A illustrates an application launching user interface 707in the form of a home screen, in various implementations, theapplication launching user interface 707 is a taskbar or a file manager.Further, although FIG. 7A illustrates only a single page of a homescreen, in various implementations, the application launching userinterface 707 includes multiple pages.

FIG. 7A illustrates a contact 750A detected at the location of thesettings representation 710.

FIG. 7B illustrates the user interface 700 of FIG. 7A in response todetecting the contact 750A at the location of the settingsrepresentation 710. In response to detecting the contact 750A at thelocation of the settings representation 710, the application launcheruser interface 707 is replaced with a general settings user interface704. The general settings user interface 704 includes a plurality ofsettings affordances 725A-725F including a connectivity managementaffordance 725A, a display management affordance 725B, a soundmanagement affordance 725C, a storage management affordance 725D, apower management affordance 725E, and a password management affordance725F. In various implementations, the general settings user interface704 can include additional, fewer, or other settings affordances.

FIG. 7B illustrates a contact 750B detected at a location of thepassword management affordance 725F.

FIG. 7C illustrates the user interface 700 of FIG. 7B in response todetecting the contact 750B at the location of the password managementaffordance 725F. In response to detecting the contact 750B at thelocation of the password management affordance 725F, the generalsettings user interface 704 is replaced with a password management userinterface 703. The password management user interface 703 includes apassword list affordance 726A that, when selected, displays a list ofuser accounts having respectively associated authentication credentials.The password management user interface 703 includes a list of accountaffordances 726B-726D that, when selected, provide information andsettable settings for respective user accounts of a list of useraccounts. The password management user interface 703 includes anadd-account affordance 726E that, when selected, allows a user to add auser account to the list of user accounts. The password management userinterface 703 includes a fetch-setting affordance 726F that, whenselected, allows a user to select a fetch setting for fetching data fromthe user accounts.

FIG. 7C illustrates a contact 750C at the location of the password listaffordance 726A.

FIG. 7D illustrates the user interface 700 in response to detecting thecontact 750C at the location of the password list affordance 726A. InFIG. 7D, the password management user interface 703 is replaced with apassword list user interface 708. The password list user interface 708includes a list of user account affordances 727A-727G respectivelyassociated with a plurality of user accounts for a respective pluralityof services and authentication credentials for those user accounts. Afew of the user account affordances 727A, 727C, 727G include an alertmarker 781 indicating the password associated with the respective useraccount is the same as the password associated with one or more otheruser accounts.

In various implementations, a toggle affordance is provided that allowsa user to toggle the display of alert markers 781. Further, in someimplementations, even when two user accounts have the same password, analert marker 781 is not shown in either user account affordance when thetwo user accounts are determined to be affiliated and shareauthentication credentials. For example, if facespace.com andhotels4less.com are affiliated, e.g., owned by the same entity and/orknown to use the same authentication credentials, no alert marker 781 isillustrated in either user account affordance 727E-727F.

The password list user interface 708 includes a search field 729 forreceiving a text input and searching the plurality of user accountsbased on the text input. The password list user interface 708 includes areturn affordance 728A for returning to the password management userinterface 703.

FIG. 7D illustrates a contact 750D detected at the location of a fourthuser account affordance 727D.

FIG. 7E illustrates the user interface 700 in response to detecting thecontact at the location of the fourth user account affordance 727D. InFIG. 7E, the password list user interface 708 is replaced with apassword details user interface 709A for a first user account for afirst service. The password details user interface 709A includes ausername affordance 730A including text indicating the usernameassociated with the first user account of the first service and apassword affordance 730B including text indicating the passwordassociated with the first user account. The password details userinterface 709A includes text indicative of websites 731A associated withthe first service. The password details user interface 709A includes areturn affordance 728B for returning to the password list user interface708.

FIG. 7F illustrates a lock screen user interface 705 as part of a userinterface 700 displayed by the portable multifunctional device 100(hereinafter “device 100”). The user interface 700 includes, in additionto the lock screen user interface 705, a device bar 701 at the top ofthe display including an identifier of the device 100 (e.g., “iPhone”),a wireless connection indicator, a current time, and a battery indicatorindicating a charge level of the device 100. In various implementations,the lock screen user interface 705 is displayed while the device 100 isin a locked state.

FIG. 7F illustrates a contact 750E detected moving upwards from alocation near the bottom of the display.

FIG. 7G illustrates the user interface 700 of FIG. 7F in response todetecting the contact 750E moving upwards from a location near thebottom of the display. In FIG. 7G, an authenticating window 741 isdisplayed indicating that an authentication process for authenticatingthe user is being performed. In various implementations, theauthentication process includes receiving authentication information andauthenticating a user based on the authentication information. Invarious implementations, the authentication information is a biometricof the user, such as one or more facial features or a fingerprint. Thus,in various implementations, the authentication information is receivedvia a camera (e.g., a depth camera) or a fingerprint sensor. In variousimplementations, the authentication information is a passcode orpassword provided by the user. Thus, in various implementations, theauthentication information is provided received via a touch-sensitivesurface.

FIG. 7H illustrates the user interface 700 of FIG. 7G in response toauthenticating the user. In FIG. 7H, the authenticating window 741 isreplaced with an authenticated window 742.

FIG. 7I illustrates the user interface 700 of FIG. 7H after unlockingthe device (e.g., placing the device 100 in an unlocked state) inresponse to authenticating the user. In FIG. 7I, the lock screen userinterface 705 is replaced with the application launcher user interface707.

FIG. 7I illustrates a verbal request 751A detected by the device 100. Invarious implementations, the verbal request 751A is displayed as part ofthe user interface 700. In various implementations, the verbal request751A is not displayed. In FIG. 7I, the verbal request 751A is a verbalrequest to display password information for a first user account.

FIG. 7J illustrates the user interface 700 of FIG. 7I in response todetecting the verbal request 751A to display the password informationfor the first user account. In FIG. 7J, an authenticating window 741 isdisplayed indicating that an authentication process for authenticatingthe user is being performed. Accordingly, in various implementations,even when the device 100 is in an unlocked state, the authenticationprocess is performed before password information is displayed. As notedabove, in various implementations, the authentication process includesreceiving authentication information and authenticating a user based onthe authentication information. In various implementations,authentication information suitable to unlock the device (e.g., apasscode) is unsuitable to display password information, which may, forexample, require more secure authentication information (e.g., abiometric of the user). However, in various implementations, theauthentication information suitable to display password informationincludes a passcode (e.g., if biometric authentication fails or is notconfigured).

FIG. 7K illustrates the user interface 700 of FIG. 7J in response toauthenticating the user. In FIG. 7K, the authenticating window 741 isreplaced with the authenticated window 742.

FIG. 7L illustrates the user interface 700 of FIG. 7K in response toauthenticating the user and responding to the verbal request 751A. InFIG. 7L, the application launcher user interface 705 is replaced withthe password details user interface 709A.

FIG. 7L illustrates a contact 750F detected at the location of passwordaffordance 730B.

FIG. 7M illustrates the user interface 700 of FIG. 7L in response todetecting the contact 750F at the location of the password affordance730B. In response to detecting the contact 750F at the location of thepassword affordance 730B, the user interface 700 includes a copyaffordance 732A that, when selected, stores the password associated withthe first user account in a cache (e.g., copies the password to aclipboard) and a share affordance 732B that, when selected, initiates aprocess for sharing the password (and/or other authenticationcredentials) associated with the first user account.

FIG. 7M illustrates a contact 750G detected at the location of the shareaffordance 732B.

FIG. 7N illustrates the user interface 700 of FIG. 7M in response todetecting the contact 750G at the location of the share affordance 732B.In FIG. 7N, the user interface 700 includes a recipient selection card733 that includes a plurality of recipient affordances 734A-734C that,when selected initiates a process for sharing the password (and/or otherauthentication credentials) associated with the first user account witha respective recipient. In various implementations, the recipientselection card 733 includes recipient affordances for nearby devices. Invarious implementations, the recipient selection card 733 includesrecipient affordances for contacts stored by the device 100.

In various implementations, the device 100 displays verificationinformation (e.g., a sequence of characters and/or visual pattern) thatis required to be entered into the device 100 (e.g., via a keyboard orfor a visual pattern, a camera) before the password (and/or otherauthentication credentials) is shared with the recipient device. Invarious implementations, the recipient device displays verificationinformation (e.g., a sequence of characters and/or visual pattern) thatis required to be entered (e.g., via a keyboard or for a visual pattern,a camera) into the device 100 before the password (and/or otherauthentication credentials) is shared with the recipient device. Anexample of requiring verification information from one device to beinput in another device is described above with reference FIGS. 6A-6H.

As compared to FIG. 7I, FIG. 7O illustrates another embodiment of theuser interface 700 of FIG. 7H after unlocking the device (e.g., placingthe device 100 in an unlocked state) in response to authenticating theuser. In FIG. 7O, the lock screen user interface 705 is replaced withthe application launcher user interface 707.

FIG. 7O illustrates a verbal request 751B detected by the device 100. Invarious implementations, the verbal request 751B is displayed as part ofthe user interface 700. In various implementations, the verbal request751B is not displayed. In FIG. 7O, the verbal request 751B is a verbalrequest to display password information for a second user account.

FIG. 7P illustrates the user interface 700 of FIG. 7O in response toauthenticating the user and responding to the verbal request 751B. InFIG. 7P, the application launcher user interface 705 is replaced withthe password details user interface 709B for a second user account for asecond service. The password details user interface 709B includes ausername affordance 730C including text indicating the usernameassociated with the second user account of the second service and apassword affordance 730D including text indicating the passwordassociated with the second user account. The password details userinterface 709B includes text indicative of websites 731B associated withthe second service. The password details user interface 709B includes areturn affordance 728B for returning to the password list user interface708.

The password details user interface 709B includes an alert 735indicating that the password associated with the second user account isthe same as a password associated with one or more other accounts. Thealert 735 includes a change-password affordance 736 that, when selected,displays a resource, e.g., a webpage or an application, for changing thepassword for the second account. In various implementations, thechange-password affordance 736 links to a general webpage/application,whereas in various implementations, the change-password affordance 736links to a password change user interface of the webpage/application. Insome embodiments, multiple services place a password change userinterface under a commonly named path, e.g.,“.well-known/change-password” and the change-password affordance 736links to this path.

FIG. 7P illustrates a contact 750H detected at the location of thechange-password affordance 736.

FIG. 7Q illustrates the user interface 700 of FIG. 7P in response todetecting the contact 750H at the location of the change-passwordaffordance 736. In FIG. 7Q, the password details user interface 709B isreplaced with a web browser user interface 702 including a userinterface for changing the password of the second user account.

As compared to FIG. 7I, FIG. 7R illustrates another embodiment of theuser interface 700 of FIG. 7H after unlocking the device (e.g., placingthe device 100 in an unlocked state) in response to authenticating theuser. In FIG. 7R, the lock screen user interface 705 is replaced withthe application launcher user interface 707.

FIG. 7R illustrates a verbal request 751C detected by the device 100. Invarious implementations, the verbal request 751C is displayed as part ofthe user interface 700. In various implementations, the verbal request751C is not displayed. In FIG. 7R, the verbal request 751C is a verbalrequest to display general password information.

FIG. 7S illustrates the user interface 700 of FIG. 7O in response toauthenticating the user and responding to the verbal request 751C. InFIG. 7S, the application launcher user interface 707 is replaced withthe password list user interface 708 (as described in detail above withrespect to FIG. 7D).

As compared to FIG. 7I, FIG. 7T illustrates another embodiment of theuser interface 700 of FIG. 7H after unlocking the device (e.g., placingthe device 100 in an unlocked state) in response to authenticating theuser. In FIG. 7T, the lock screen user interface 705 is replaced withthe application launcher user interface 707.

FIG. 7T illustrates a verbal request 751D detected by the device 100. Invarious implementations, the verbal request 751D is displayed as part ofthe user interface 700. In various implementations, the verbal request751D is not displayed. In FIG. 7T, the verbal request 751D is a verbalrequest to display password information for a third user account.

FIG. 7U illustrates the user interface 700 of FIG. 7T in response toauthenticating the user and responding to the verbal request 751D.Because the third user account is not one of the user accounts of thelist of user accounts 727A-727G, the application launcher user interface707 is replaced with the password list user interface 708 (as describedin detail above with respect to FIG. 7D) rather than a password detailsuser interface 709A-709B. However, in FIG. 7U, the search field 729 isprepopulated based on the verbal request and the list of user accounts727A-727G is sorted based on the prepopulation of the search field 729.In some embodiments, the list of user accounts is filtered based on theprepopulation of the search field 729 such that user accounts notmatching the prepopulation of the search field 729 are not displayed.

As compared to FIG. 7F, FIG. 7V illustrates a lock screen user interface705 as part of a user interface 700 displayed by the portablemultifunctional device 100 (hereinafter “device 100”).

FIG. 7V illustrates a verbal request 751E detected by the device 100. Invarious implementations, the verbal request 751E is displayed as part ofthe user interface 700. In various implementations, the verbal request751E is not displayed. In FIG. 7V, the verbal request 751D is a verbalrequest to display password information for the first user account.

FIG. 7W illustrates the user interface of FIG. 7V in response todetecting the verbal request to display password information for thefirst user account. In FIG. 7W, an authenticating window 741 isdisplayed indicating that an authentication process for authenticatingthe user is being performed.

FIG. 7X illustrates the user interface 700 of FIG. 7W in response toauthenticating the user. In FIG. 7X, the authenticating window 741 isreplaced with an authenticated window 742.

FIG. 7Y illustrates the user interface 700 of FIG. 7X after unlockingthe device (e.g., placing the device 100 in an unlocked state) inresponse to authenticating the user and responding to the verbal request751E. In FIG. 7Y, the lock screen user interface 705 is replaced withthe password details user interface 709A.

FIGS. 8A-8C illustrate a flow diagram of a method 800 of generating anew password for a user account in accordance with some embodiments. Themethod 800 is performed at an electronic device (e.g., the portablemultifunction device 100 in FIG. 1A, or the device 300 in FIG. 3) with adisplay device and one or more input devices. In some embodiments, thedisplay device is a touch-screen display and one or more of the inputdevices are on or integrated with the display device. In someembodiments, the display device is separate from the one or more inputdevices. Some operations in method 800 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, the method 800 provides an intuitive way to generatea new password for a user account. The method 800 reduces the cognitiveburden on a user when generating a new password for a user account,thereby creating a more efficient human-machine interface. Forbattery-operated electronic devices, enabling a user to generate a newpassword for a user account faster and more efficiently conserves powerand increases the time between battery charges.

The device displays (802), on the display device, a user interface thatincludes a new-password field. In various implementations, the userinterface includes an electronic form including a plurality of fields.For example, in FIG. 5B, the device 100 displays a web browser userinterface 502 that includes a new-password field 532C.

The device detects (804), via the one or more input devices, a userinput that corresponds to selection of the new-password field. Invarious implementations, the user input includes a contact at thelocation of the new-password field, a click while a cursor is at thelocation of the new-password field, tabbing to the new-password field,or selecting a next affordance while a field arranged in an order beforethe new-password field is selected. For example, in FIG. 5F, the device100 detects a contact 550F at the location of the new-password field532C. As another example, with reference to FIG. 5F, a user input thatcorresponds to selection of the new-password field can include a contactat the location of the next affordance in the navigation region 541.

In some embodiments, detecting the user input that corresponds toselection of the new-password field includes determining that a selectedfield is a new-password field (806) based on one or more of a number offields of the user interface or text associated with the user interface.For example, in FIG. 5F, the device 100 classifies the field selected bythe contact 550F as a new-password field based on the text reading“password” next to the selected field, the text reading “register” inthe address bar 521, the number of the plurality of fields 532A-532Dbeing greater than two, and/or the number of fields having text reading“password” next to the field being more than one. By determining thatthe selected field is a new-password field (as opposed to a differenttype of field), the user interface provides different options inresponse to detecting different types of fields and, thus, provides anefficient mechanism for a user to perform various different actions,thereby reducing the amount of user interaction to perform the variousactions. The reduction in user interaction reduces wear-and-tear of thedevice. The reduction in user interaction also results in fasterperformance of the various actions and, thus, reduces power drain toperform the various actions, increasing battery life of the device.

In response to detecting the user input that corresponds to selection tothe new-password field (808), the device displays (810), on the displaydevice, a representation of a new automatically-generated password inthe new-password field. Automatically generating a new password for auser account provides an efficient mechanism for a user to generate anew password for a user account, thus reducing the amount of userinteraction to generate a new password for a user account. The reductionin user interaction reduces wear-and-tear of the device. The reductionin user interaction also results in faster generation of the newpassword for the user account and, thus, reduces power drain to generatethe new password for the user account, increasing battery life of thedevice. Further, automatically generating the new password for the useraccount provides a unique, strong, and/or secure password for the useraccount, increasing security for user account.

In some embodiments, the device displays (812) the newautomatically-generated password. For example, in FIG. 5G1, the device100 displays the new automatically-generated password in thenew-password field 532G. Displaying the new password provides the userwith a sense of security, increasing the likelihood that the user willaccept the new password, reducing user interaction to generate adifferent new password. Reducing the user interaction reduceswear-and-tear of the device and reduces power drain, increasing batterylife of the device.

In some embodiments, the device displays (814) a generic passwordindicator. For example, in FIG. 5G2, the device 100 displays a series ofasterisks (or bullets) in the new-password field 532C. Displaying ageneric password indicator (rather than the new password) reduces userconfusion during user account registration and, in particular, passwordgeneration, reducing user interaction during the registration. Reducingthe user interaction reduces wear-and-tear of the device and reducespower drain, increasing battery life of the device.

In some embodiments, the device displays (816) a portion of the newautomatically-generated password and an indication that a portion of thenew automatically-generated password is not displayed. For example, inFIG. 5G3, the device 100 displays a portion of the newautomatically-generated password and an indication that a portion of thenew automatically-generated password is not displayed, e.g., thevisibility of the new automatically-generated password decreases alongits length by fading. Displaying a portion of the new password providesthe benefits of both of the above embodiments, providing the user with asense of security while reducing user confusion, thereby reducing userinteraction with the device. Reducing the user interaction reduceswear-and-tear of the device and reduces power drain, increasing batterylife of the device.

In some embodiments, the new automatically-generated password isgenerated (818) based on one or more password generation constraints ofthe user interface. For example, in FIG. 5G1, the newautomatically-generated password includes an uppercase letter (e.g., Y),a lowercase letter (e.g., v), a number (e.g., 2), a special character(e.g., %), and at least a threshold number of characters. Automaticallygenerating the password based on password generation constraints of theuser interface increases the likelihood of the user accepting thepassword and reduces the probability that the password will be rejectedby the service, ultimately reducing the amount of user interaction withthe device. Reducing the user interaction reduces wear-and-tear of thedevice and reduces power drain, increasing battery life of the device.Further, adhering to the password generation constraints of the userinterface increases the strength of the password, resulting in increasedsecurity for the user account.

Further in response to detecting the user input that corresponds toselection of the new-password field (808), the device displays (820), onthe display device, an affordance to accept the newautomatically-generated password and an affordance to decline to use thenew automatically-generated password. For example, in FIG. 5G3, thedevice 100 displays the accept affordance 543A and the declineaffordance 543B. Displaying the affordance to accept the new password(and the representation of the new password) in response to detectingthe user input that corresponds to selection of the new-password field(as opposed to, e.g., user input requesting that the device provide anew automatically-generated password) increases the likelihood that theuser will accept the new password and reduces user interaction togenerate a new password. Thus, security for the user account isincreased and the reduction in user interaction reduces wear-and-tear ofthe device and reduces power drain, increasing battery life of thedevice.

In some embodiments, the device displays (822) a new-password userinterface including the affordance to accept the newautomatically-generated password and the affordance to decline to usethe new automatically-generated password. For example, in FIG. 5G3, thedevice 100 displays the new-password user interface 503C that includesthe accept affordance 543A and the decline affordance 543B.

In some embodiments, the device displays (824) the new-password userinterface excluding display of a plurality of character insertionaffordances displayed in a soft keyboard. For example, in FIG. 5G3, thedevice 100 displays the new-password user interface 503C, but does notdisplay the soft keyboard 503A of FIG. 5C (or the numeric soft keyboard503B of FIG. 5E). Excluding display of the soft keyboard increases thelikelihood that the user will accept the new password, resulting inincreased security and reduced user interaction with the device.Further, excluding display of the soft keyboard uses less space on thescreen; thus, a smaller (and less expensive) screen can provide the sameusability.

In some embodiments, the device detects (826), via the one or more inputdevices, a user input that corresponds to a selection of a useridentifier field. In various implementations, the user identifier fieldincludes a username field, an e-mail address field, a phone numberfield, etc. For example, in FIG. 5B, the device 100 detects a contact550B at the location of the username field 532A. As another example, inFIG. 5D, the device 100 detects a contact 550D at the location of thephone number field 532B. In some embodiments, in response to detectingthe user input that corresponds to a selection of the user identifierfield, the device displays (828), on the display device, the softkeyboard including the plurality of character insertion affordances. Forexample, in FIG. 5C, in response to detecting the contact 550B at thelocation of the username field 532A, the device 100 displays the softkeyboard 503A. As another example, in FIG. 5E, in response to detectingthe contact 550D at the location of the phone number field 532B, thedevice 100 displays the numeric soft keyboard 503B. Providing differentuser interfaces in response to detecting different types of fieldsprovides an efficient mechanism for a user to perform various differentactions, thus reducing the amount of user interaction to perform thevarious actions. The reduction in user interaction reduces wear-and-tearof the device and increases battery life of the device.

In some embodiments, the new-password user interface includes (830) adescription of the new automatically-generated password and instructionsfor retrieval of the new automatically-generated password. For example,in FIG. 5G3, the new-password user interface 503C includes text 544including a description of the new automatically-generated password andinstructions for retrieval of the new automatically-generated password.In particular, the text 544 indicates that the newautomatically-generated password has been automatically generated andsatisfies a password strength requirement. The text 544 indicates thatthe new automatically-generated password will be saved by the device 100and can be accessed by the user, e.g., via a verbal request. Including adescription of the new password and instructions for retrieval increasesthe likelihood that the user will accept the new password and reducesuser interaction to generate a new password. Thus, security for the useraccount is increased and the reduction in user interaction reduceswear-and-tear of the device and reduces power drain, increasing batterylife of the device.

In some embodiments, the device displays (832), separate from thenew-password user interface, a second affordance to decline to use thenew automatically-generated password. For example, in FIG. 5G3, thedevice 100 displays a secondary decline affordance 543BB to decline thenew automatically-generated password separate from the new-password userinterface, in particular, next to the representation of the newautomatically-generated password in the new-password field 532C.Displaying a second affordance to decline to use the new passwordresults in a more efficient human-machine interface as a user may moreeasily find a mechanism to decline to use the new password. Forbattery-operated electronic devices, a more efficient human-machine userinterface conserves power and increases the time between batterycharges. Further, a more efficient human-machine user interface reducesthe amount of user interaction with the device and reduces wear-and-tearof the device.

In some embodiments, the device detects (834), via the one or more inputdevices, a user input corresponding to a selection of the affordance toaccept the new automatically-generated password. For example, in FIG.5I, the device 100 detects a contact 550H at the location of the acceptaffordance 543A. In some embodiments, in response to detecting the userinput corresponding to the selection of the affordance to accept the newautomatically-generated password, the device ceases to display (836) theaffordance to accept the new automatically-generated password and theaffordance to decline to use the new automatically-generated password.For example, in FIG. 5J, in response to detecting the contact 550H atthe location of the accept affordance 543A, the device ceases to displaythe new-password user interface 503C including the accept affordance543A and the decline affordance 543B.

In some embodiments, the device detects (838), via the one or more inputdevices, a user input corresponding to a selection of the affordance todecline to use the new automatically-generated password. For example, inFIG. 5G3, the device 100 detects a contact 550G at the location of thedecline affordance 543B. In some embodiments, in response to detectingthe user input corresponding to the selection of the affordance toaccept the new automatically-generated password, the device replaces(840) the affordance to accept the new automatically-generated passwordand the affordance to decline to use the new automatically-generatedpassword with a soft keyboard including a plurality of characterinsertion affordances. For example, in FIG. 5H, in response to detectingthe contact 550G at the location of the decline affordance 543B, thedevice 100 replaces the new-password user interface 503C including theaccept affordance 543A and the decline affordance 543B with the softkeyboard 503B. Replacing the new-password user interface with the softkeyboard provides an efficient mechanism for the user to generate a newpassword, thus reducing the amount of user interaction to generate thenew password. The reduction in user interaction reduces wear-and-tear ofthe device. The reduction in user interaction also results in fastergeneration of the new password and, thus, reduces power drain to performthe storage management operations, increasing battery life of thedevice.

It should be understood that the particular order in which theoperations in FIGS. 8A-8C have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 900, 1000, and 1100) are also applicable in an analogous mannerto method 800 described above with respect to FIGS. 8A-8C. For example,the user interfaces (including the fields, affordances, and responsesthereof), user inputs, password representations, and authenticationcredentials described above with reference to method 800 optionally haveone or more of the characteristics of the user interfaces (including thefields, affordances, and responses thereof), user inputs, passwordrepresentations, and authentication credentials described herein withreference to other methods described herein (e.g., methods 900, 1000,and 1100). For brevity, these details are not repeated here.

FIGS. 9A-9D illustrate a flow diagram of a method 900 of inserting averification code into a user interface in accordance with someembodiments. The method 900 is performed at an electronic device (e.g.,the portable multifunction device 100 in FIG. 1A, or the device 300 inFIG. 3) with a display device and one or more input devices. In someembodiments, the display device is a touch-screen display and one ormore of the input devices are on or integrated with the display device.In some embodiments, the display device is separate from the one or moreinput devices. Some operations in method 900 are, optionally, combinedand/or the order of some operations is, optionally, changed.

As described below, the method 900 provides an intuitive way to insert averification code into a user interface. The method 900 reduces thecognitive burden on a user when inserting a verification code into auser interface, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user toinsert a verification code into a user interface faster and moreefficiently conserves power and increases the time between batterycharges.

The device receives (902), via the one or more input devices, a requestto access a resource protected by a verification code. In variousimplementations, the verification code is a one-time use code oron-demand code that is sent via an authorized communication channel,such as via text or email. In various implementations, the requestincludes selection of a login affordance or selection of a request-codeaffordance. For example, in FIG. 5M, the device 100 detects a contact550L at the location of the continue-sign-in affordance 531E.

After receiving the request to access the resource, the device receives(904), at the electronic device, an electronic message. In variousimplementations, the electronic message is an SMS text message, ane-mail, or a chat message. For example, in FIG. 5O, the device 100displays a message notification 561A indicating that a text message hasbeen received. However, in various implementations as described below,the device receives the electronic message without displaying a messagenotification.

In some embodiments, in response to receiving the electronic message,the device displays (906), on the display device, a messagenotification. For example, in FIG. 5O, in response to receiving theelectronic message, the device 100 displays the message notification561A. In some embodiments, the message notification includes (908) acopy affordance that, when selected, copies the content to a clipboard.For example, in FIG. 5U2, the device 100 displays the messagenotification 561A including the copy affordance 561C. The copyaffordance provides an efficient mechanism for a user to insert theverification code without manually inserting each character of theverification code, reducing user interaction with the device. Thereduction in user interaction reduces wear-and-tear of the device. Thereduction in user interaction also results in faster insertion of theverification code and, thus, reduces power drain to insert theverification code, increasing battery life of the device.

In some embodiments, the device detects (910), via the one or moreinputs, a user input corresponding to selection of the messagenotification. For example, in FIG. 5O, the device 100 detects thecontact 550M at the location of the message notification 561A. In someembodiments, in response to detecting the user input corresponding toselection of the message notification, the device displays (912), on thedisplay device, the electronic message with emphasis of the content thatmatches the predetermined format (as described further below withrespect to block 916). For example, in FIG. 5P, the device 100 displaysthe message window 564 including the content of the electronic messagereceived from the source, with emphasis (e.g., underlining) of thecontent that matches the predetermined format (e.g., the verificationcode “03201981”). Displaying the electronic message in response todetecting selection of the message notification results in a moreefficient human-machine interface (as a user need not access anapplication launcher user interface to launch an application to displaythe electronic message). Further, displaying the electronic message withemphasis of the content that matches the predetermined format guides theuser to quickly find the verification code, resulting in a moreefficient human-machine interface. For battery-operated electronicdevices, a more efficient human-machine user interface conserves powerand increases the time between battery charges. Further, a moreefficient human-machine user interface reduces the amount of userinteraction with the device and reduces wear-and-tear of the device.

In some embodiments, in response to receiving the electronic message,the device (914), in accordance with a determination that the electronicmessage does not include content that meets the respective criteria (asdescribed further below with respect to block 916), displays, on thedisplay device, a message notification and, in accordance with adetermination that the electronic message includes content that meetsthe respective criteria, forgoes display of (or suppresses) the messagenotification. For example, in FIG. 5AC, in accordance with adetermination that the received text message does not include averification code, the device 100 displays the message notification561F. However, in FIG. 5AB, in accordance with a determination that thereceived text message includes a verification code, the device 100forgoes display of a message notification. Forgoing display of themessage notification simplifies the process of inserting theverification code, decreasing the likelihood that the user will launchthe application by which the electronic message was received andincreasing the likelihood the user will insert the verification codeusing an insertion affordance. This decreases user interaction with thedevice, reducing wear-and-tear and increasing battery life.

After receiving the electronic message and while displaying, on thedisplay device, a user interface for inputting the verification code: inaccordance with a determination that the electronic message includescontent that meets respective criteria, wherein the respective criteriainclude a format requirement that the electronic message includescontent that matches a predetermined format, the device displays (916),on the display device, an insertion affordance that, when selected,automatically inserts the content that matches the predetermined formatas a verification code in the user interface. For example, in FIG. 5Z,after receiving the text message that prompted display of the messagenotification 561A in FIG. 5Y and while displaying the web browser userinterface 502 including the verification code field 532G, in accordancewith a determination that the text message includes a verification code,the device 100 displays the insertion affordance 545 that, when selectedinserts the verification code in the verification code field 532G. Theinsertion affordance provides an efficient mechanism for a user toinsert the verification code, thus reducing the amount of userinteraction to insert the verification code. The reduction in userinteraction reduces wear-and-tear of the device. The reduction in userinteraction also results in faster initiation of the performance of thestorage management operations and, thus, reduces power drain to performthe storage management operations, increasing battery life of thedevice.

In some embodiments, the respective criteria include (918) a timingrequirement that the user interface for inputting the verification codeis displayed within a predetermined time period from when the messagewas received. For example, in FIG. 5Z, the device 100 displays theinsertion affordance 545 in accordance with a determination that theverification code field 532G is selected within three minutes ofreceiving the text message that prompted display of the messagenotification 561A in FIG. 5Y. Displaying the insertion affordance for alimited time increases the likelihood that the user will select theinsertion affordance and decreases the likelihood that the insertionaffordance will be displayed when the user in unlikely to select theinsertion affordance, saving space on the screen. By using less space onthe screen, a smaller (and less expensive) screen can provide the sameusability.

In some embodiments, the respective criteria include (920) acharacteristic requirement that the user interface for inputting theverification code includes a text entry field having predeterminedcharacteristics. For example, in FIG. 5Z, the device 100 displays theinsertion affordance 545 in accordance with a determination that the webbrowser user interface 502 includes the verification code field 532G. Insome embodiments, the respective criteria include (922) a selectionrequirement that the text entry field having the predeterminedcharacteristics is selected. For example, in FIG. 5Z, the device 100displays the insertion affordance 545 in accordance with a determinationthat the verification code field 532G is selected (e.g., by detectingthe contact 550V in FIG. 5Y). Displaying the insertion affordance when averification code field is selected increases the likelihood that theuser will select the insertion affordance and decreases the likelihoodthat the insertion affordance will be displayed when the user inunlikely to select the insertion affordance, saving space on the screen.By using less space on the screen, a smaller (and less expensive) screencan provide the same usability.

In some embodiments, the predetermined format is based on (924) text ofthe electronic message. For example, in FIG. 5Z, the device 100 displaysthe insertion affordance 545 in accordance with detecting the text“code” in the text message that prompted display of the messagenotification 561A in FIG. 5Y. In some embodiments, the predeterminedformat is based on (926) the content including a string of characterssatisfying a predetermined character criteria. For example, in FIG. 5Z,the device 100 displays the insertion affordance 545 in accordance withdetecting the string of characters (“03201981”) including a series ofeight numbers.

In some embodiments, the insertion affordance is displayed (928) inconjunction with a soft keyboard including a plurality of characterinsertion affordances. For example, in FIG. 5Z, the device 100 displaysthe insertion affordance 545 as part of the numeric soft keyboard 503B,above a plurality of character insertion affordances. In someembodiments, the insertion affordance is displayed (930) in a textsuggestion region. For example, in FIG. 5Z, the device 100 displays theinsertion affordance 545 in the text suggestion region of the numericsoft keyboard 503B. In various implementations, the text suggestionregion is above the soft keyboard, located on a touch bar, or within apop-up menu. Displaying the insertion affordance in conjunction with asoft keyboard provides a more efficient human-machine interface byproviding different options to the user (e.g., use the insertionaffordance or type the verification code using the soft keyboard)without additional user interaction to access the different options.Reducing the amount of user interaction with the device reduceswear-and-tear of the device and increases battery life of the device.

In some embodiments, the insertion affordance includes (932) anindication of the application by which the electronic message wasreceived. For example, in FIG. 5Z, the insertion affordance 545 includesan indication that the verification code was received from a textmessaging application. In some embodiments, the insertion affordanceincludes (934) an indication of the sender of the electronic message.For example, in FIG. 5Z, the insertion affordance 545 includes anindication that the verification code was received from phone number“987-66.” Including an indication of the application and/or sender ofthe electronic message increases the likelihood that the user willselect the insertion affordance and efficiently insert the verificationcode, reducing user interaction with the device to insert theverification code in other ways. Reducing the amount of user interactionwith the device reduces wear-and-tear of the device and increasesbattery life of the device.

In some embodiments, after receiving the electronic message and whiledisplaying, on the display device, a user interface for inputting theverification code: in accordance with a determination that theelectronic message does not include content that meets the respectivecriteria, the device forgoes display (936) of the insertion affordance.For example, in FIG. 5AD, after receiving the text message that prompteddisplay of the message notification 561F in FIG. 5AC and whiledisplaying the web browser user interface 502 including the verificationcode field 532G, in accordance with a determination that the textmessage does not include verification code, the device 100 does notdisplay the insertion affordance 545. In some embodiments, in accordancewith a determination that the electronic message does not includecontent that meets the respective criteria, the device displays (938),on the display device, one or more alternate insertion affordances that,when selected, automatically enters respective words in the userinterface. For example, in FIG. 5AD, the device 100 displays alternateinsertion affordances in the text suggestion region 542.

In some embodiments, the device detects (940), via the one or more inputdevices, a user input corresponding to selection of the insertionaffordance. For example, in FIG. 5Z, the device 100 detects the contact550W at the location of the insertion affordance 545. In someembodiments, in response to detecting the user input corresponding tothe selection of the insertion affordance, the device automaticallyinserts (942) the content that matches the predetermined format as averification code in the user interface. For example, in FIG. 5AA, thedevice 100 inserts the verification code “03201981” in the verificationcode field 532G. Automatically inserting the verification code in theuser interface provides an efficient human-machine interface forinserting the verification code. For battery-operated electronicdevices, a more efficient human-machine user interface conserves powerand increases the time between battery charges. Further, a moreefficient human-machine user interface reduces the amount of userinteraction with the device and reduces wear-and-tear of the device.

In some embodiments, in response to the determination that theelectronic message includes the content that meets the respectivecriteria, the device automatically inserts (944) the content thatmatches the predetermined format as a verification code in the userinterface. For example, in FIG. 5AB, in response to receiving the textmessage the prompted display of the message notification 561A in FIG. Y,the device 100 automatically inserts the verification code “03201981” inthe verification code field 532G. Automatically inserting theverification code in the user interface provides an efficienthuman-machine interface for inserting the verification code. Forbattery-operated electronic devices, a more efficient human-machine userinterface conserves power and increases the time between batterycharges. Further, a more efficient human-machine user interface reducesthe amount of user interaction with the device and reduces wear-and-tearof the device.

It should be understood that the particular order in which theoperations in FIGS. 9A-9D have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 800, 1000, and 1100) are also applicable in an analogous mannerto method 900 described above with respect to FIGS. 9A-9D. For example,the user interfaces (including the fields, affordances, and responsesthereof), user inputs, notifications, and criteria described above withreference to method 900 optionally have one or more of thecharacteristics of the user interfaces (including the fields,affordances, and responses thereof), user inputs, notifications, andcriteria described herein with reference to other methods describedherein (e.g., methods 800, 1000, and 1100). For brevity, these detailsare not repeated here.

FIGS. 10A-10C illustrate a flow diagram of a method 1000 of sharingauthentication credentials in accordance with some embodiments. Themethod 1000 is performed at a first electronic device (e.g., theportable multifunction device 100 in FIG. 1A, or the device 300 in FIG.3) with a display device and one or more input devices. In someembodiments, the display device is a touch-screen display and one ormore of the input devices are on or integrated with the display device.In some embodiments, the display device is separate from the one or moreinput devices. Some operations in method 1000 are, optionally, combinedand/or the order of some operations is, optionally, changed.

As described below, the method 1000 provides an intuitive way to shareauthentication credentials. The method 1000 reduces the cognitive burdenon a user when sharing authentication credentials, thereby creating amore efficient human-machine interface. For battery-operated electronicdevices, enabling a user to share authentication credentials faster andmore efficiently conserves power and increases the time between batterycharges.

The first electronic device receives (1002), at the first electronicdevice, an indication that a second electronic device is in need ofauthentication credentials for a service. For example, in FIG. 6D, thefirst electronic device 610 displays a sharing confirmation window 640in response to receiving an indication that the second electronic device620 is in need of authentication credentials for a service.

In response to receiving the indication that the second electronicdevice is in need of authentication credentials for the service, inaccordance with a determination that the first electronic device meetsrespective criteria, wherein the respective criteria include arequirement that the first electronic device is within a predeterminedproximity to the second electronic device, the first electronic devicedisplays (1004), on the display device in order for the respectivecriteria to be met, a verification prompt that requires input ofverification information from the second electronic device on the firstelectronic device in order to proceed. For example, in FIG. 6E, thefirst electronic device 610 displays the first user interface 612including a verification prompt that requires input of information fromthe second electronic device 620 (e.g., the verification informationdisplayed by the second electronic device 620) on the first electronicdevice 610 in order to proceed.

In some embodiments, in accordance with a determination that the firstelectronic device does not meet the respective criteria, the firstelectronic device forgoes display (1006) of the verification prompt. Forexample, in FIG. 6E, a third electronic device which does not meet therespective criteria forgoes display of the verification prompt. Forgoingdisplay of the verification prompt on user devices that are notproximate to the second electronic devices provides a more efficienthuman-machine interface, reducing the amount of user interaction todismiss the verification prompt and using less space on the screen forunnecessary information. For battery-operated electronic devices, a moreefficient human-machine user interface conserves power and increases thetime between battery charges. Further, a more efficient human-machineuser interface reduces the amount of user interaction with the deviceand reduces wear-and-tear of the device. By using less space on thescreen, a smaller (and less expensive) screen can provide the sameusability.

In some embodiments, the respective criteria include (1008) arequirement that the first electronic device is within a proximity to athird electronic device that is associated with the second electronicdevice. In some embodiments, the second electronic device is (1010) amedia playback device and the third electronic device is a remotecontrol for the second electronic device. For example, in FIG. 6E, thefirst electronic device 610 displays the verification prompt inaccordance with its proximity to the third electronic device 630.

In some embodiments, the first electronic device displays (1012), on thedisplay device, a sharing confirmation notification including a sharingconfirmation affordance that, when selected, causes display of theverification prompt and detects, via the one or more input devices, auser input corresponding to selection of the sharing confirmationaffordance. For example, in FIG. 6E, the first electronic device 610displays the sharing confirmation window 640 that includes the sharingconfirmation affordance 641 and detects the contact 650C at the locationof the sharing confirmation affordance 641. The sharing confirmationwindow decreases the likelihood that authentication credentials would beshared accidentally. Thus, the security of the user account isincreased.

In some embodiments, the verification information from the secondelectronic device is (1014) displayed by the second electronic device.For example, in FIG. 6E, the verification information from the secondelectronic device 620 is displayed by the second electronic device 620on the display device 621.

While displaying the verification prompt, the first electronic devicereceives (1016), via the one or more input devices, the verificationinformation from the second electronic device on the first electronicdevice. For example, in FIG. 6E, the first electronic device detects thecontact 650D (and additional contacts) corresponding to the verificationinformation displayed by the second electronic device 620.

In some embodiments, the verification prompt is (1018) for establishinga secure connection between the first electronic device and the secondelectronic device and receiving the verification information from thesecond electronic device on the first electronic device includesreceiving an input that satisfies the conditions for establishing thesecure connection between the first electronic device and the secondelectronic device.

In response to receiving the verification information, the firstelectronic device initiates (1020) a process for sharing authenticationcredentials for the service from the first electronic device to thesecond electronic device. For example, in FIG. 6F, in response toreceiving the verification information, the first electronic device 610displays the service selection user interface 508 including a list ofservice affordances 661A-661G respectively associated a plurality ofservices, user accounts for those services, and authenticationcredentials for those user accounts and, in FIG. 6G, in response todetecting a selection of a particular service, shares authenticationcredentials for the service from the first electronic device 610 to thesecond electronic device 620. Sharing the authentication credentialsprovides an efficient mechanism for a user to input authenticationcredentials on the second electronic device without using other userinteraction. The reduction in user interaction reduces wear-and-tear ofthe device. The reduction in user interaction also results in fasterinitiation of inputting authentication credentials on the secondelectronic device and, thus, reduces power drain to input theauthentication credentials, increasing battery life of the device.

In some embodiments, the first electronic device detects (1022), via theone or more input devices, a sequence of one or more inputs to shareauthentication credentials for the service. For example, in FIG. 6F, thedevice detects the contact 650E at the location of the first serviceaffordance 661A and, in response, shares the authentication credentialsfor the first service from the first electronic device 610 to the secondelectronic device 620.

In some embodiments, the first electronic device displays (1024), on thedisplay device a service list including a plurality of serviceaffordances respectively corresponding to a plurality of servicesrespectively associated with a plurality of authentication credentials.For example, in FIG. 6F, the first electronic device 610 displays theservice selection user interface 508 including a list of serviceaffordances 661A-661G respectively associated a plurality of services,user accounts for those services, and authentication credentials forthose user accounts.

In some embodiments, the first electronic device sorts (1026) theservice list based at least in part on relevance of the respectiveservices. In various implementations, the relevant of the respectiveservices is based on a domain name, application name, or identifier forthe service requesting credentials supplied by the second device andapplied by the first device. For example, in FIG. 6F, the indicationthat the second electronic device 620 is in need of authenticationcredentials for a service indicates the service and that service islisted at the top of the list of service affordances 661A-661G. Sortingthe service list provides an efficient mechanism for the user to selectthe service affordance associated with the intended service, reducinguser interaction with the device and increasing security by reducing thelikelihood that the user will share authentication credentials (e.g.,for another user account) accidentally.

In some embodiments, the first electronic device detects (1028), via theone or more input devices, a user input corresponding to a selection ofone of the plurality of service affordances corresponding to the serviceassociated with the authentication credentials for the service. Forexample, in FIG. 6F, the device detects the contact 650E at the locationof the first service affordance 661A and, in response, shares theauthentication credentials for the first service from the firstelectronic device 610 to the second electronic device 620.

In some embodiments, in response to detecting the sequence of one ormore inputs, the first electronic device shares (1030) authenticationcredentials for the service from the first electronic device to thesecond electronic device. For example, in FIG. 6G, in response todetecting the contact 650E at the location of the first serviceaffordance 661A in FIG. 6F, the first electronic device 610 sharesauthentication credentials for the first service from the firstelectronic device 610 to the second electronic device 620.

In some embodiments, the first electronic device transmits (1032), fromthe first electronic device to the second electronic device, theauthentication credentials for the service wirelessly over a secureconnection. For example, the authentication credentials can betransmitted via a peer-to-peer WiFi connection or a Bluetoothconnection. In some embodiments, the first electronic device shares(1034) authentication credentials including a user identifier and apassword from the first electronic device to the second electronicdevice.

In some embodiments, before transmitting the authentication credentials,the first electronic device authenticates the user. Thus, in someembodiments, the first electronic device obtains (1036), via the one ormore input devices, authentication information and authenticates (1038)the user based on the authentication information. Authenticating theuser before sharing the authentication credentials increases security ofthe user account by decreasing the likelihood that the authenticationcredentials would be shared without the user's knowledge.

In some embodiments, after the process for sharing the authenticationcredentials for the service, the first electronic device displays(1040), on the display device, a notification indicating that theprocess for sharing the authentication credentials for the service iscompleted. For example, in FIG. 6G, the first electronic device 610displays a complete-sharing window 643 including a notificationindicating that the authentication credentials having been shared withthe second electronic device 620.

It should be understood that the particular order in which theoperations in FIGS. 10A-10C have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 800, 900, and 1100) are also applicable in an analogous mannerto method 1000 described above with respect to FIGS. 10A-10C. Forexample, the user interfaces (including the fields, affordances, andresponses thereof), the user inputs, the electronic devices, and theauthentication credentials described above with reference to method 1000optionally have one or more of the characteristics of the userinterfaces (including the fields, affordances, and responses thereof),the user inputs, the electronic devices, and the authenticationcredentials described herein with reference to other methods describedherein (e.g., methods 800, 900, and 1100). For brevity, these detailsare not repeated here.

FIGS. 11A-11C illustrate a flow diagram of a method 1100 of displayingpassword information in accordance with some embodiments. The method1100 is performed at an electronic device (e.g., the portablemultifunction device 100 in FIG. 1A, or the device 300 in FIG. 3) with adisplay device and one or more input devices. In some embodiments, thedisplay device is a touch-screen display and one or more of the inputdevices are on or integrated with the display device. In someembodiments, the display device is separate from the one or more inputdevices. Some operations in method 1100 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, the method 1100 provides an intuitive way to displaypassword information. The method 1100 reduces the cognitive burden on auser when displaying password information, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to displaying password information faster andmore efficiently conserves power and increases the time between batterycharges.

The device detects (1102), via the one or more input devices, a verbalrequest to display password information. In various implementations, thedevice detects the verbal request via a microphone. For example, in FIG.7I, the device 100 detects a verbal request 751A to display passwordinformation. As another example, in FIG. 7O, the device 100 detects averbal request 751B to display password information. As another example,in FIG. 7R, the device 100 detects a verbal request 751C to displaypassword information. As another example, in FIG. 7T, the device 100detects a verbal request 751D to display password information.

In response to receiving the verbal request to display the passwordinformation, in accordance with a determination that the request is fora password for a first user account that is accessible by the device andthat the user is authenticated, the device displays (1104) the passwordfor the first user account. For example, in FIG. 7L, in accordance witha determination that the verbal request 751A is for a password for theuser account associated with the fourth user account affordance 727D ofFIG. 7D and after authenticating the user (as illustrated in FIGS.7J-7K), the device 100 displays a password affordance 730B includingtext indicating the password associated with that user account. Asanother example, in FIG. 7P, in accordance with a determination that theverbal request 751B is for a password for the user account associatedwith the seventh user account affordance 727G of FIG. 7D and afterauthenticating the user, the device 100 displays a password affordance730D including text indicating the password associated with that useraccount. Displaying password information in response to a verbal requestprovides an efficient mechanism for displaying password information,thus reducing the amount of user interaction to display passwordinformation. The reduction in user interaction reduces wear-and-tear ofthe device. The reduction in user interaction also results in fasterinitiation of displaying password information and, thus, reduces powerdrain to display password information, increasing battery life of thedevice.

In some embodiments, the device displays (1106) information regardingthe first user account that is accessible by the device. For example, inFIG. 7L, the device 100 displays the password details user interface709A including a username affordance 730A including text indicating theusername associated with the user account of the service, a passwordaffordance 730B including text indicating the password associated withthe user account, and text indicative of websites 731A associated withthe service of the user account. As another example, in FIG. 7P, thedevice 100 displays the password details user interface 709B including ausername affordance 730C including text indicating the usernameassociated with the user account of the service, a password affordance730D including text indicating the password associated with the useraccount, and text indicative of websites 731B associated with theservice of the user account. Providing additional information about thefirst user account increases user confidence regarding the display ofthe first password, decreasing the likelihood that the user will performfurther user interaction to display the first password. Decreasing userinteraction reduces wear-and-tear of the device and increases batterylife of the device.

In some embodiments, the information regarding the first user accountthat is accessible by the device includes (1108) password securityinformation for the password for the first user account. In someembodiments, the information regarding the first user account that isaccessible by the device includes (1110) an alert indicating that thepassword for the first user account is the same as a password foranother user account that is accessible by the device. For example, inFIG. 7P, the device 100 displays an alert 735 indicating that thepassword associated with the second user account is the same as apassword associated with one or more other accounts. In someembodiments, the password security information for the password for thefirst user account includes information regarding a strength of thepassword, e.g., if it is easily guessed, is short, is low-entropy,contains common words, etc. In some embodiments, the alert includes(1112) an affordance that, when selected, displays a resource forchanging the password for the first user account. For example, in FIG.7P, the alert 735 includes the change-password affordance 736 that, whenselected, displays a resource, e.g., a webpage or an application, forchanging the password for the user account. Providing an affordance forchanging a weak or duplicative password provides an efficient mechanismfor a user to change a password, thus reducing the amount of userinteraction to change the password. The reduction in user interactionreduces wear-and-tear of the device. The reduction in user interactionalso results in faster initiation of changing the password and, thus,reduces power drain to change the password, increasing battery life ofthe device. Further, providing an efficient mechanism for a user tochange the password increases the likelihood that a user will performsuch an action and increase security of the user account.

In response to receiving the verbal request to display the passwordinformation, in accordance with a determination that the request is fora password for a second user account that is accessible by the deviceand that the user is authenticated, the device displays (1114) thepassword for the second user account. For example, in FIG. 7L, inaccordance with a determination that the verbal request 751A is for apassword for the user account associated with the fourth user accountaffordance 727D of FIG. 7D and after authenticating the user (asillustrated in FIGS. 7J-7K), the device 100 displays a passwordaffordance 730B including text indicating the password associated withthat user account. As another example, in FIG. 7P, in accordance, inaccordance with a determination that the verbal request 751B is for apassword for the user account associated with the seventh user accountaffordance 727G of FIG. 7G and after authenticating the user, the device100 displays a password affordance 730D including text indicating thepassword associated with that user account.

In some embodiments, in response to receiving the verbal request todisplay the password information and in accordance with a determinationthat the request is for general password information, the devicedisplays (1116) a list of password display affordances which, whenselected, displays a respective password of a respective user accountaccessible by the device. For example, in FIG. 7S, in response toreceiving the verbal request 751C in FIG. 7R, the device 100 displaysthe password list user interface 708 that includes a list of useraccount affordances 727A-727G respectively associated with a pluralityof user accounts with a respective plurality of services andauthentication credentials for those user accounts. Displaying passwordinformation in response to a verbal request provides an efficientmechanism for displaying password information, thus reducing the amountof user interaction to display password information. The reduction inuser interaction reduces wear-and-tear of the device. The reduction inuser interaction also results in faster initiation of displayingpassword information and, thus, reduces power drain to display passwordinformation, increasing battery life of the device.

In some embodiments, in response to receiving the verbal request todisplay the password information and in accordance with a determinationthat the request is for a password of user account not accessible by thedevice, the device displays (1118) a list of password displayaffordances which, when selected, displays a respective password of arespective user account accessible by the device. For example, in FIG.7U, in response to receiving the verbal request 751D in FIG. 7T, thedevice 100 displays the password list user interface 708 that includes alist of user account affordances 727A-727G respectively associated witha plurality of user accounts with a respective plurality of services andauthentication credentials for those user accounts. In some embodiments,the device displays (1120) a search field prepopulated based on theverbal request. For example, in FIG. 7U, the search field 729 isprepopulated with the word “Hotels” based on the verbal request 751D inFIG. 7T.

In some embodiments, the device detects (1122), via the one or moreinput devices, a user input corresponding to a selection of the passwordof the first user account. For example, in FIG. 7L, the device 100detects the contact 7520F at the location of the password affordance730B. In some embodiments, in response to detecting the user inputcorresponding to selection of the password of the first user account,the device displays (1124), on the display device, a share affordancewhich, when selected, initiates a process for sharing the password ofthe first user account. For example, in FIG. 7M, the device 100 displaysthe share affordance 732B that, when selected, initiates a process forsharing the password (and/or other authentication credentials)associated with the first user account. Thus, the user interfaceprovides an efficient mechanism for a user to share authenticationcredentials, reducing the amount of user interaction to shareauthentication credentials. The reduction in user interaction reduceswear-and-tear of the device. The reduction in user interaction alsoresults in faster initiation of the sharing of authenticationcredentials and, thus, reduces power drain to share authenticationcredentials, increasing battery life of the device.

In some embodiments, the device detects (1126), via the one or moreinput devices, a user input corresponding to a selection of the shareaffordance. For example, in FIG. 7M, the device 100 detects the contact750G at the location of the share affordance 732B. In some embodiments,In response to detecting the user input corresponding to selection ofthe share affordance, the device displays (1128), on the display device,a recipient selection card including one or more recipient affordanceswhich, when selected, shares the password of the first user account witha respective device. For example, in FIG. 7N, the device 100 displaysthe recipient selection card 733 that includes the plurality ofrecipient affordances 734A-734C that, when selected initiates a processfor sharing the password (and/or other authentication credentials)associated with the first user account with a respective recipient.

In some embodiments, in response to receiving the verbal request todisplay the password information and in accordance with a determinationthat the user is not authenticated, the device authenticates the userand proceeds to display the requested password information. Thus, insome embodiments, in response to receiving the verbal request to displaythe password information and in accordance with a determination that theuser is not authenticated, the device obtains (1130), via the one ormore input devices, authentication information and authenticates theuser based on the authentication information. For example, in FIGS.7J-7K, in response to detecting the verbal request 751A, the device 100obtains, via the one or more input devices, authentication information(as illustrated by the authenticated window 741 of FIG. 7J) andauthenticates the user based on the authentication information (asillustrated by the authenticated window 742 of FIG. 7K). In someembodiments, the authentication information includes (1132) a biometricof the user, such as facial features or a fingerprint. Authenticatingthe user increases the security of the user account by ensuring that thepassword information will not be displayed without the user's knowledge.

In some embodiments, prior to receiving the verbal request to displaythe password information and while the device is locked, the devicedetects (1134), via the one or more input devices, a user inputrequesting unlocking the device; in response to the user inputrequesting unlocking the device, the device obtains, via the one or moreinput devices, unlocking information; and the device unlocks the devicebased on the unlocking information. For example, in FIG. 7F, the device100 detects a user input requesting unlocking the device in the form ofthe contact 750E detected moving upwards from a location near the bottomof the display. In FIG. 7G, the device 100 obtains unlocking information(as illustrated by the authenticating window 741). In FIG. 7H, thedevice 100 unlocks the device 100 based on the unlocking information (asillustrated by the authenticated window 742).

In some embodiments, the unlocking information includes (1136) apasscode and the authentication information includes a biometric of theuser or, if a biometric authentication fails, a passcode. Thus, invarious implementations, the authentication information is more securethan the unlocking information. However, in various implementations, theauthentication information includes a passcode (e.g., if biometricauthentication fails, if biometric authentication fails twice, or is notconfigured).

In some embodiments, authentication information is obtained (1138) whilethe device is locked and wherein authenticating the user based on theauthentication information further includes unlocking the device basedon the authentication information. For example, in FIG. 7W, the device100 obtains authentication information (as illustrated by theauthenticating window 741) while the device is locked (as indicated bythe lock screen user interface 705). In FIG. 7Y, the device 100 isunlocked (as indicated by the password details user interface 709A)based on the authentication information. Unlocking the device andauthenticating the user based on the same information results in a moreefficient human-machine interface (as a user need not separately unlockthe device and authenticate). For battery-operated electronic devices, amore efficient human-machine user interface conserves power andincreases the time between battery charges. Further, a more efficienthuman-machine user interface reduces the amount of user interaction withthe device and reduces wear-and-tear of the device.

It should be understood that the particular order in which theoperations in FIGS. 11A-11C have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 800, 900, and 1000) are also applicable in an analogous mannerto method 1100 described above with respect to FIGS. 11A-11C. Forexample, the user interfaces (including the fields, affordances, andresponses thereof), the user inputs (in particular, verbal requests andcommands), and authentication credentials, described above withreference to method 1100 optionally have one or more of thecharacteristics of the user interfaces (including the fields,affordances, and responses thereof), the user inputs (in particular,verbal requests and commands), and authentication credentials, describedherein with reference to other methods described herein (e.g., methods800, 900, and 1000). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 8A-8C, 9A-9D,10A-10C, and 11A-11C are, optionally, implemented by components depictedin FIGS. 1A-1B. For example, display operation 802, detection operation804, display operation 810, display operation 820, reception operation902, reception operation 904, display operation 916, reception operation1002, display operation 1004, reception operation 1016, initiationoperation 1020, detection operation 1102, display operation 1104, ordisplay operation 1114 are, optionally, implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method comprising: at an electronic device with a display device and one or more input devices: displaying, on the display device, a user interface that includes a new-password field; detecting, via the one or more input devices, a user input that corresponds to selection of the new-password field; and in response to detecting the user input that corresponds to selection of the new-password field: displaying, on the display device, a representation of a new automatically-generated password in the new-password field; and displaying, on the display device, an affordance to accept the new automatically-generated password and an affordance to decline to use the new automatically-generated password.
 2. The method of claim 1, wherein displaying the representation of the new automatically-generated password includes displaying the new automatically-generated password.
 3. The method of claim 1, wherein displaying the representation of the new automatically-generated password includes displaying a portion of the new automatically-generated password and an indication that a portion of the new automatically-generated password is not displayed.
 4. The method of claim 1, wherein displaying the representation of the new automatically-generated password includes displaying a generic password indicator.
 5. The method of claim 1, wherein displaying the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password includes displaying a new-password user interface including the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password.
 6. The method of claim 5, wherein, displaying the new-password user interface excludes display of a plurality of character insertion affordances displayed in a soft keyboard.
 7. The method of claim 6, further comprising: detecting, via the one or more input devices, a user input that corresponds to selection of a user identifier field; and in response to detecting the user input that corresponds to selection of the user identifier field, displaying, on the display device, the soft keyboard including the plurality of character insertion affordances.
 8. The method of claim 5, wherein the new-password user interface further includes a description of the new automatically-generated password and instructions for retrieval of the new automatically-generated password.
 9. The method of claim 5, wherein displaying the new-password user interface further includes displaying, separate from the new-password user interface, a second affordance to decline to use the new automatically-generated password.
 10. The method of claim 1, further comprising: detecting, via the one or more input devices, a user input corresponding to a selection of the affordance to accept the new automatically-generated password; and in response to detecting the user input corresponding to the selection of the affordance to accept the new automatically-generated password, ceasing to display the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password.
 11. The method of claim 1, further comprising: detecting, via the one or more input devices, a user input corresponding to a selection of the affordance to decline to use the new automatically-generated password; and in response to detecting the user input corresponding to the selection of the affordance to accept the new automatically-generated password, replacing the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password with a soft keyboard including a plurality of character insertion affordances.
 12. The method of claim 1, wherein detecting the user input that corresponds to selection of the new-password field includes determining that a selected field is a new-password field based on one or more of a number of fields of the user interface or text associated with the user interface.
 13. The method of claim 1, wherein the new automatically-generated password is generated based on one or more password generation constraints of the user interface.
 14. An electronic device comprising: a display device configured to display a user interface; one or more input devices configured to receive inputs; and a processing device coupled with the display device and the one or more input devices, the processing device configured to: display, on the display device, a user interface that includes a new-password field; detect, via the one or more input devices, a user input that corresponds to selection of the new-password field; and in response to detecting the user input that corresponds to selection of the new-password field: display, on the display device, a representation of a new automatically-generated password in the new-password field; and display, on the display device, an affordance to accept the new automatically-generated password and an affordance to decline to use the new automatically-generated password.
 15. The electronic device of claim 14, wherein the processing device is configured to display the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password by displaying a new-password user interface including the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password.
 16. The electronic device of claim 15, wherein, the processing device is configured to display the new-password user interface without displaying a plurality of character insertion affordances displayed in a soft keyboard.
 17. The electronic device of claim 16, wherein the processing device is further configured to: detect, via the one or more input devices, a user input that corresponds to selection of a user identifier field; and in response to detecting the user input that corresponds to selection of the user identifier field, display, on the display device, the soft keyboard including the plurality of character insertion affordances.
 18. The electronic device of claim 14, wherein the processing device is further configured to: detect, via the one or more input devices, a user input corresponding to a selection of the affordance to accept the new automatically-generated password; and in response to detecting the user input corresponding to the selection of the affordance to accept the new automatically-generated password, cease to display the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password.
 19. The electronic device of claim 14, wherein the processing device is further to: detect, via the one or more input devices, a user input corresponding to a selection of the affordance to decline to use the new automatically-generated password; and in response to detecting the user input corresponding to the selection of the affordance to accept the new automatically-generated password, replace the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password with a soft keyboard including a plurality of character insertion affordances.
 20. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, that, when executed by an electronic device with a display device and one or more input devices, cause the electronic device to: display, on the display device, a user interface that includes a new-password field; detect, via the one or more input devices, a user input that corresponds to selection of the new-password field; and in response to detecting the user input that corresponds to selection of the new-password field: display, on the display device, a representation of a new automatically-generated password in the new-password field; and display, on the display device, an affordance to accept the new automatically-generated password and an affordance to decline to use the new automatically-generated password.
 21. The non-transitory computer readable storage medium of claim 20, wherein the instructions, when executed, caused the electronic device to display the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password by displaying a new-password user interface including the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password.
 22. The non-transitory computer readable storage medium of claim 21, wherein, the instructions, when executed, caused the electronic device to display the new-password user interface without displaying of a plurality of character insertion affordances displayed in a soft keyboard.
 23. The non-transitory computer readable storage medium of claim 22, where the instructions, when executed further cause the electronic device to: detect, via the one or more input devices, a user input that corresponds to selection of a user identifier field; and in response to detecting the user input that corresponds to selection of the user identifier field, display, on the display device, the soft keyboard including the plurality of character insertion affordances.
 24. The non-transitory computer readable storage medium of claim 21, wherein the new-password user interface further includes a description of the new automatically-generated password and instructions for retrieval of the new automatically-generated password.
 25. The non-transitory computer readable storage medium of claim 21, wherein the instructions, when executed, cause the electronic device to display the new-password user interface by displaying, separate from the new-password user interface, a second affordance to decline to use the new automatically-generated password.
 26. The non-transitory computer readable storage medium of claim 20, wherein the instructions, when executed, further cause the electronic device to: detect, via the one or more input devices, a user input corresponding to a selection of the affordance to accept the new automatically-generated password; and in response to detecting the user input corresponding to the selection of the affordance to accept the new automatically-generated password, cease to display the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password.
 27. The non-transitory computer readable storage medium of claim 20, wherein the instructions, when executed, further cause the electronic device to: detect, via the one or more input devices, a user input corresponding to a selection of the affordance to decline to use the new automatically-generated password; and in response to detecting the user input corresponding to the selection of the affordance to accept the new automatically-generated password, replace the affordance to accept the new automatically-generated password and the affordance to decline to use the new automatically-generated password with a soft keyboard including a plurality of character insertion affordances. 